home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr35
/
spitfire.zip
/
SPITFIRE.DOC
< prev
next >
Wrap
Text File
|
1993-04-24
|
209KB
|
3,836 lines
_________________________________________________________________________
___________________ ___________________
________________ S P I T F I R E ________________
_____________ ------------------------- _____________
__________ Bulletin Board System __________
_______ for MS/PC DOS _______
____ Personal Computers ____
_______________________________
____ ____
____ Version 2.5 ____
___________________
Copyright (C) 1987, 88 by Mike Woltz
------------------------------------------
Buffalo Creek Software
------------------------------------------
>>> Release Date October 22, 1988 <<<
------------------------------------------
TABLE OF CONTENTS
---------------------
# Section Title Page #
+--+------------------------------------------------+------+
Introduction..................................... 1
[1] 1.0 Important Notice............................ 1
1.1 Copyright & Registered Trademark Notice..... 2
[2] 2.0 Spitfire Hardware Requirements.............. 3
2.1 Modems...................................... 4
2.2 Numeric Result Codes........................ 4
2.3 Modem Initialization........................ 4
2.4 Getting Started............................. 5
2.5 Spitfire File Paths......................... 11
[3] 3.0 Spitfire System Files....................... 12
3.1 Spitfire Work Files......................... 13
3.2 Spitfire Display Files...................... 14
3.3 Spitfire Menu Files......................... 16
3.4 Spitfire File Clarifications................ 19
3.5 About Spitfire Display Files................ 22
3.6 Backup Files................................ 22
3.7 THOUGHTS.BBS................................ 23
[4] 4.0 Command Line Parameters..................... 23
4.1 SF.BAT...................................... 24
[5] 5.0 Setting Up The System Records............... 24
[6] 6.0 Spitfire Questionnaires..................... 27
[7] 7.0 The Function Keys........................... 28
7.1 Function Key Definitions.................... 28
[8] 8.0 The ALT Keys................................ 30
8.1 Available Keys.............................. 30
8.2 ALT Key Definitions......................... 31
[9] 9.0 Main Menu Explained......................... 32
9.1 Main Menu Example........................... 33
9.2 Explanation of Main Menu Features........... 33
[10] 10.0 Message Menu Explained...................... 36
10.1 Message Menu Example........................ 36
10.2 Message Menu Explanation.................... 36
[11] 11.0 File Menu Example........................... 39
11.1 File Menu Explanation....................... 39
11.2 Upload/Download Protocols................... 42
[12] 12.0 Sysop Menu Explained........................ 42
12.1 Sysop Menu Explanation...................... 43
TABLE OF CONTENTS (cont)
---------------------
# Section Title Page #
+--+------------------------------------------------+------+
[13] 13.0 Special Commands For Sysop Status........... 47
[14] 14.0 Hardware/Software Data Flow Control......... 48
[15] 15.0 Screen Save Feature......................... 48
[16] 16.0 SPITFIRE Doors Feature...................... 48
16.1 SPITFIRE Doors Display Files................ 50
16.2 SPITFIRE Doors Support...................... 51
[17] 17.0 External File Transfer Protocols............ 51
17.1 External Download Protocols................. 51
17.2 External Upload Protocols................... 54
17.3 External Protocol Support................... 57
[18] 18.0 Spitfire Technical Reference Information.... 57
[19] 19.0 Comment From The Author..................... 61
[20] 20.0 SPITFIRE Utilities.......................... 62
Appendix A Modem Initialization Strings................ 65
Appendix B Registered SPITFIRE Boards.................. 66
Appendix C SPITFIRE Questions and Answers.............. 67
Page 1
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
INTRODUCTION
------------
SPITFIRE is a bulletin board program written in Borland's Turbo
Pascal (Version 5.0). Designed on an IBM Personal Computer, SPITFIRE
is compatible with MS/PC DOS machines (IBM "Compatibles").
SPITFIRE is distributed under the "Shareware" concept. You are
encouraged to distribute this software to others, in its original,
unmodified condition, as long as you DO NOT charge for this program
in any way, shape or form.
1.0 - IMPORTANT NOTICE!
-----------------------
Thank you for taking the time and expense to obtain SPITFIRE.
Surely, after you've had a chance to look SPITFIRE over, you'll agree
it is a powerful bulletin board program which combines both speed,
flexibility and user ease.
This program, like many others, is distributed under the
"Shareware" concept. Since that SPITFIRE is not a program which
appeals to a mass market, your support is vital. SPITFIRE can be
utilized on a trial basis for not more than thirty (30) days or 500
callers, whichever comes first. In the event this software is used
beyond the trial period, then a registration fee of $65.00 is required.
Your registration of SPITFIRE will provide you with full support
and notification of future updates and revisions of SPITFIRE. Such
support and notification may be terminated at any time without notice.
Many of you will be running SPITFIRE 24 hours per day, 7 days per
week. This is more than any other program you'll use. Considering
that, it becomes apparent that the registration fee is truly minimal.
____________________________________________________________________
| |
| Registration is simple & easy. Send a $65.00 registration fee to: |
|____________________________________________________________________|
| _____________________________ |
| | | |
| | Buffalo Creek Software | |
| | Attn: Mike Woltz | |
| | 913 - 39th Street | |
| | West Des Moines, Iowa 50265 | |
| |_____________________________| |
|_________________________________|
Page 2
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
Mike Woltz and Buffalo Creek Software shall not be held responsible
for any damage incurred by the user to hardware, software, or
peripheral devices while running SPITFIRE. All responsibility lies
with the user of the software.
No part of this manual may be reproduced, transmitted, transcribed,
stored in a retrieval system, or translated into any language (natural
or computer), in any form or by any means, without the prior
written permission of Mike Woltz.
THIS SOFTWARE IS NOT FOR SALE! You are granted a limited license
to use the software described in this manual. The software may be used
or copied only in accordance with the terms set forth herein.
You may not make any changes or modifications to SPITFIRE, and you
may not de-compile, disassemble, or otherwise reverse-engineer it. You
may not rent or lease it to others.
No fee, charge or other compensation may be accepted or requested
by anyone without express written permission from Mike Woltz. This
includes disk vendors.
Operators of electronic bulletin board systems (Sysops) may post
SPITFIRE for downloading by their users without written permission
only as long as the conditions set forth herein are met. A fee may be
charged for access to the BBS as long as no specific fee is charged
for access to the SPITFIRE files.
Distributors of public domain and user supported software, such
as disk vending services, may distribute copies of SPITFIRE subject to
the above conditions only after obtaining written permission from Mike
Woltz.
1.1 - COPYRIGHT & REGISTERED TRADEMARK NOTICE
---------------------------------------------
SPITFIRE and affiliate programs distributed with it are not to be
modified or distributed in modified form without the express written
consent of Mike Woltz.
SPITFIRE is NOT to be sold, used or modified for, or with, illegal
intent under the penalty of law.
`SPITFIRE' is Copyright (C) 1987, 88 by Mike Woltz
`SPITFIRE' is a registered trademark of Buffalo Creek Software.
Page 3
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
`Turbo Pascal' is a registered trademark of Borland International Corp.
`BRK' is Copyright (C) 1985, by Solid Systems
`SEALINK' is (C) Copyright 1986 by System Enhancement Associates
`WILDFIRE' is Copyright (C) 1988 by Stephen L. Cox
`DSZ' is Copyright (C) 1988 by Omen Technology INC
2.0 - SPITFIRE HARDWARE REQUIREMENTS
------------------------------------
The following are considered the minimum equipment requirements
for running SPITFIRE:
[1] At least 320K Memory
[2] Fixed Disk (preferable) - Two disk drives will work
[3] Modem (US Robotics or Hayes preferable)
[4] Monitor
SPITFIRE requires several files being open at the same time.
For this reason, you will need to have the following files and buffers
set in your system's CONFIG.SYS file located in your root directory.
SPITFIRE may not work properly if this is not done!
CONFIG.SYS should have the following settings:
FILES=25
BUFFERS=30
DEVICE=ANSI.SYS
DEVICE=BRK.DRV
The "DEVICE=BRK.DRV" is optional, however, if your system supports
the use of SPITFIRE Doors or External File Transfer Protocols, then the
use of BRK (or some similar utility) is certainly recommended. More
information regarding the use of BRK is provided in the External File
Protocols Section of this manual.
If you are unfamiliar with how CONFIG.SYS works, consult your DOS
manual.
SPITFIRE includes an option which allows the Sysop to shell to
DOS from within the program. For this to work properly, you MUST have
a copy of COMMAND.COM in the root directory of the drive in which
SPITFIRE.EXE resides.
Page 4
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
2.1 - MODEMS
------------
SPITFIRE automatically determines your incoming callers' baud
rates. In order for this to work, your modem must be able to send
numeric result codes. Appendix A contains a list of modems and their
corresponding initialization strings which have been tested to work
with SPITFIRE.
2.2 - NUMERIC RESULT CODES
--------------------------
SPITFIRE determines the baud rate of incoming calls by receiving
the numeric result code from your modem when the modem establishes
carrier detect. Check your (Modem) owner's manual for these numeric
codes.
Note that these codes can be changed within SPITFIRE by selecting
ALT+M while SPITFIRE is waiting for a caller. SPITFIRE defaults to the
codes listed below:
300 Baud # 1
1200 Baud # 5
2400 Baud # 10
9600 Baud # 17
Error-checking modems
-----------------------
1200 Baud # 15
2400 Baud # 16
9600 Baud # 17
The SPITFIRE default modem initialization string seems to work with
most modems. The Hayes 2400 (and possibly other Hayes Smartmodems)
requires a unique initialization string that will be found in Appendix
A of this manual.
2.3 - MODEM INITIALIZATION
--------------------------
SPITFIRE automatically sends an "ATZ", pauses 1.5 seconds and then
sends the configured modem initialization string to the modem after
each call. This procedure seems to work fine for most modems. If you
are using a Hayes 2400 Smartmodem or a Everex internal 2400 or are
having difficulties, it is suggested you try the string listed below:
AT&C1&D2&T5M0H0X1V0E0S2=1S0=0
Page 5
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
SPITFIRE'S default initialization string (listed below) seems to
work fine with most modems:
ATS0=1Q0V0E0M0H0S2=1X1
In the event you are using an USR HST and wish to run your BBS
at 19200 baud, then the below listed initialization string works:
ATS0=1&B1&N0&H3&R2&Y3Q0V0E0M0H0S2=1X1
Should you need to change the modem initialization string, you
select ALT+M at the "SPITFIRE ready for caller" prompt. Appendix A
contains a complete listing of modems which have been tested with
SPITFIRE and their known corresponding initialization strings. The
modem initialization string can also be altered at the DOS prompt by
entering the following command line parameters:
SPITFIRE /M ATS0=1Q0V0E0M0H0S2=1X1 (Your Initialization String)
Using the same command line parameters, the modem initialization
string can be included within the SF.BAT file. Please note, however,
the command line parameters set in SF.BAT will always override those
set by using ALT+M at the "SPITFIRE ready for caller" prompt.
2.4 GETTING STARTED
--------------------
If you're like most, you're probably not too thrilled with the
prospect of reading a gargantuan document such as this. Most folks are
going to boot this program and try to run SPITFIRE without reading
further, so here are some quick guidelines regarding your initial setup
of SPITFIRE.
[1] Create a directory named SF on the drive on which you intend
to run SPITFIRE. Copy all SYSTEM FILES into your newly
created SF directory. (Listed in Section 3.0)
[2] You should have received a file named SF.BAT with your
SPITFIRE package. You may need to use your favorite text
editor (as long as it saves in ASCII format) to modify
this file. Examine the default values (such as target &
source drives) and configure them to suit your needs.
Page 6
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
(Example: Default on drive specification is C: and if
you're running SPITFIRE on drive D, then you'll have to
change it to D:). After finishing that, look for the line
that contains SPITFIRE /I2400 /C1. "/I2400" indicates the
top speed of your modem. You may have to change this to the
highest speed your modem is capable of. (Example: If you
have a 9600 baud modem, change the string to read
"SPITFIRE /I9600 /C1" or "SPITFIRE /I19200 /C1"). "/C1"
indicates the COM port you are using. If you are using
COM port 2, you need to change the string to read
"SPITFIRE /I2400 /C2". After you've made your changes,
be certain to save your modified file to disk.
[3] Now you are ready to boot SPITFIRE by using your SF.BAT
file. When first booting SPITFIRE, you will get the prompt
"SFSYSDAT.SYS not found! Do you wish to create it? [y/n]".
Answer "Y" and SPITFIRE will create one. Next you will get
the prompt "SFUSERS.DAT not found! Do you wish to create
it? [y/n]". Answer "Y" and SPITFIRE will create one. Then
you will get the prompt "SFSYSINF.SYS not found! Do you
wish to create it? [y/n]". Answer "Y" and SPITFIRE will
create one. The first thing we have to be concerned with
is the dilemma of not having properly assigned the correct
COM port. In this event you will get a message that states
"Comm Port Number ? is not responding! Spitfire halting."
If that happens, refer to step number 2 in this Section. If
all goes well, shortly after that, you will be prompted for
the Sysop Name. The name you enter here is the name that
users will see credited as Sysop of the system. In all
probability, you will wish to enter your real full name.
After that, SPITFIRE will ask you for a Sysop User Name.
It is recommended you answer this prompt with "Sysop". All
comments left by your users will be left to this name you
have chosen. At this time SPITFIRE will prompt you to input
password, phone number, city and state and birthdate.
SPITFIRE uses the responses you enter here to automatically
add you as the first user in the SFUSERS.DAT file.
If your modem is malfunctioning, is turned off or not
connected, SPITFIRE will then relay the message "Your modem
is not responding properly! Do you wish to continue? [y/n]".
Answer "Y" and SPITFIRE will prompt "SPITFIRE ready for
caller at [CURRENT TIME]". Hit ALT+M to change the modem
initialization string that is proper for your modem.
Page 7
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
[4] At the "SPITFIRE ready for caller..." prompt, press ALT+S to
log on locally as Sysop. When asked for your name, you must
enter the same name as you entered as the Sysop User Name at
the beginning of the boot. (If you use the name "Sysop", the
system will ask for a last name. Here you can simply hit
<RETURN> and continue.) Then enter the password you have
selected previously. When you get to the Main Menu, press
F2 and set your security level to 999. Then log off in a
normal fashion.
[5] At the "SPITFIRE ready for caller" prompt, press ALT+Z.
Pressing ALT+Z opens the window which allows you to
configure SPITFIRE. The commands that you will see
are listed as such below:
--[ SPITFIRE CONFIGURATION ]--
<1> Sysop User Name...............: Sysop
<2> Sysop Security................: 50
<3> New User Security.............: 10
<4> New User Log On Time..........: 45
<5> 300 Baud Users................: Not Allowed
<6> Daily Time Limit..............: 60
<7> Log On Time Limit.............: 60
<8> Type of BBS...................: Public BBS
<9> Maximum Users.................: 500
<10> Maximum User Calls Per Day....: 10
<11> Number Of Callers.............: 1
<12> Graphics......................: Ansi Available
<13> Second Password...............: Second Password Required
<14> Page..........................: On
<15> Upload/Download Ratio Prompt..: 10
<16> Upload Time Compensation......: 1.000
<17> Drop to DOS Password..........: Spitfire
<18> BBS Starting Date.............: October 22, 1988
ENTER COMMAND [<Q>... Quit]:
Command <1> Allows you to change the Sysop User Name.
Command <2> Allows you to change the Sysop security level. Any
user with an access equal to or greater than this
numeric value can read all messages (public and
private), move messages, undelete messages, delete
any message and overwrite existing files during
uploading (if the filename already exists).
Page 8
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
Command <3> Allows you to set the default security level for a new
user.
Command <4> Allows you to set the amount of time on the board for
the new user's visit. (First day only)
Command <5> Toggles whether you are going to allow 300 baud users.
The system will display the file NO300.BBS to the
screen and log a 300 baud caller off if you do not
allow 300 baud callers.
Command <6> Sets the amount of time per day a user is allowed on
the board. See Section 3.4 for more information on
setting time limits.
Command <7> Sets the amount of time per call, per user. See
Section 3.4 for more information.
Command <8> Toggles whether you are going to have a PRIVATE or a
PUBLIC BBS. If you toggle this as a Private BBS, then
the user attempting to log on must be in the users
file to be granted access. If you have the system
toggled as a Private BBS and a caller tries to log on
as new user, the system will display PRIVATE.BBS and
log the caller off.
Command <9> Determines the amount of users you will allow to
utilize your BBS. (i.e. - If you have this value set
at 500 and you already have 500 users and a new user
(501) tries to log on, the system displays the file
MAXUSERS.BBS and logs the user off.)
Command <10> This sets the limit of how many times a user can call
your board per day. If this amount is exceeded, the
system will display TOOMANY.BBS and log the user off.
Command <11> This gives you the opportunity to set the number of
callers. The reason for this is if you are already
running an established board, you can enter the
the current number of callers, so as not to start
the BBS with Caller Number 1.
Command <12> Toggles whether or not you wish to offer Ansi
graphics. If you wish to offer Ansi graphics, you
must create .CLR files to match the display .BBS
files you have: (i.e. - ALL.BBS {non-Ansi} & ALL.CLR
Page 9
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
{Ansi Graphics}). In order for you to see the Ansi
Graphics locally, you must have DEVICE=ANSI.SYS in
your CONFIG.SYS file.
Command <13> Toggles password prompt. If turned on, then after
entering the first password, the system prompts the
users for their birth date. Should the users not know
their birth date, the system will log them off.
Command <14> Toggles the Page on and off. If the Page is on and
you are paged a Prompt Bell is sounded to alert you
to the page. If the Page is toggled off and a user
pages you, you don't receive the page and the system
displays SFPAGED.BBS/CLR to the screen, which normally
is written to notify the user that you are not
available to chat.
Command <15> Sets the ratio of downloads to uploads. (i.e. - If a
user uploads 1 file and downloads x amount of files
that exceeds the "x" amount, then after the download
is completed, SPITFIRE sends SFRATIO.BBS unless
DAILYLMT.DAT instructs SPITFIRE not to). SFRATIO.BBS
is normally written to notify the users that their
upload/download ratio is unacceptable.
Command <16> This sets the time compensation for time used during
an upload. The default is 1.000. Should you wish to
have the user rewarded with extra time for an upload,
you can increase this numeric value.
Command <17> Sets the password that is needed to drop to DOS from a
remote location. The default is "Spitfire", but you
will wish to change this for the sake of security.
Command <18> This provides an opportunity to set the starting date
of your bulletin board. The reason for this is if you
are already running an established board, you can
enter the original starting date of your BBS
rather than the date of your conversion to SPITFIRE.
After setting your configuration for SPITFIRE enter <Q>
to Quit and you are returned to the "Ready..." prompt.
[6] You must now set the file paths you wish to use to run
SPITFIRE. This is done by pressing ALT+P at the
"Ready..." prompt. Pressing ALT+P opens the window which
allows you to set the file paths which will be used in
running SPITFIRE. The commands that you will see are
listed as such below:
Page 10
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
--[SPITFIRE FILE PATHS]--
<1> External Transfer Protocols......: Yes
<2> Work Files Path..................: C:\SF\WORK
<3> Display Files Path...............: C:\SF\DISPLAY
<4> External Transfer Path...........: C:\SF\EXTERNAL
ENTER COMMAND [ <Q>...Quit] :
Command <1> Toggles whether you wish to implement the use of
the external transfer protocol feature.
Command <2> Allows you to specify the directory in which the
SPITFIRE Work Files reside. (For more information
on this refer to Section 2.5 - File Paths.) All
files which belong in the Work File Path are
specified as such with a (WORK) in the file
description in Section 3.1 - SPITFIRE work files.
Command <3> Allows you to specify the directory in which the
SPITFIRE Display Files reside. All files with a
BBS or CLR extension are Display Files and should
reside in the directory you designate here. (For
more information refer to Secion 2.5 - File Paths.)
All files which belong in the Display File Path are
specified as such with a (DISPLAY) in the file
description in Section 3.2 - SPITFIRE display files.
Command <4> Allows you to specify the directory from which you
opt to run the SPITFIRE External Transfer Protocols.
All files which you are using to run the External
Transfer Protocols must reside in the directory you
designate here. (For more information on the External
Transfer Protocols refer to Section 17.0 - External
File Transfer Protocols.)
Establishing specified file paths will provide the Sysop with more
manageable directories. However, if the Sysop prefers, all files
can be accessed from the SF directory. Simply enter C:\SF
in response to each of the above files path questions.
After you've configured SPITFIRE to meet your specifications,
Quit and return to the "SPITFIRE ready for caller..." prompt.
At the "SPITFIRE ready for caller..." prompt, hit ALT+R to
configure your system records. For more information on this feature,
refer to Section 5.0 of this manual.
Page 11
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
After you've completed that, you're ready to go!
If you're having problems running SPITFIRE, and you're sure you've
tried everything, gather together a report of your version number and
all the information pertaining to the difficulties (such as System,
Modem, Comm Port) you are experiencing and contact Buffalo Creek's BBS
(515-225-8496) for registered support. Be as thorough as possible so
an accurate determination of the cause of your problem(s) can be made.
Every effort will be made to determine and correct the problem!
Further, if you had a problem that isn't covered by this manual
and were able to work it out without registered support, please contact
Buffalo Creek's BBS so the information you have discovered can be
shared with other users of SPITFIRE. Also, please report any unique
configurations you may discover so everyone will benefit from your
ideas.
2.5 SPITFIRE FILE PATHS
-----------------------
SPITFIRE supports file paths for the files which are accessed in
the process of its execution. The Sysop has the option of placing all
SPITFIRE files into the SF directory (SYSTEM) or, if preferred, setting
up separate directories for the WORK, DISPLAY and EXTERNAL files.
Designating individual file paths for your WORK, DISPLAY and EXTERNAL
files can help make your directories more manageable.
The SYSTEM files path contains files which are required for the
execution of SPITFIRE. The WORK files path contains files which
SPITFIRE accesses and writes to periodically in the process of the
program execution. The DISPLAY files path contains all files which
are displayed to user while logged on the BBS. The EXTERNAL files path
includes files necessary to provide the user with optional
transfer protocols other than those automatically accessed from
within SPITFIRE.
**NOTE** All DISPLAY files are optional. Should the Sysop choose
not to use these available files, SPITFIRE will operate perfectly
fine. In fact, SPITFIRE will display a default message in a number
of incidences if the optional display file is not found. The DISPLAY
files merely provide an additional means by which the Sysop can create
unique screens to personalize their BBS system.
Page 12
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
The system files MUST reside in the SF directory that was created
when setting up SPITFIRE. The WORK, DISPLAY and EXTERNAL file paths
are set by pressing ALT-P at the "SPITFIRE Ready For Caller" prompt.
(Refer to Section 2.4)
The following sections, 3.0 through 4.0, discuss individually
files used by SPITFIRE. After the file description, a (SYSTEM),
(WORK) or (DISPLAY) is included to help you in determine in which
directory the file should be placed. No files which will be used
in your External Protocol Path will be found. These are not included
in the SPITFIRE package because they are separate programs written
by other programmers.
3.0 - SPITFIRE SYSTEM FILES
---------------------------
There are four file types that comprise SPITFIRE and allow it
to function: System, Work, Display and External Protocol.
The first type is referred to as SYSTEM FILES. System Files
are mandatory for SPITFIRE's operation and MUST reside in your main
SPITFIRE directory from which you run SPITFIRE. These files are
accessed frequently by SPITFIRE during program operation.
SPITFIRE.EXE - Main System Program (SYSTEM)
SFMAIN .MNU - Spitfire Main Menu (SYSTEM)
SFMSG .MNU - Spitfire Message Menu (SYSTEM)
SFFILE .MNU - Spitfire File Menu (SYSTEM)
SFSYSOP .MNU - Spitfire Sysop Menu (SYSTEM)
The above-mentioned files MUST be present for SPITFIRE to
run. SPITFIRE will halt if these files are not found in the directory
in which you are running your system.
The following system files will be created by SPITFIRE if they
are not already present.
SFSYSDAT.SYS - Starting date, number of callers, etc (SYSTEM)
SFSYSINF.SYS - File paths, descriptions, etc (SYSTEM)
SFEVENTS.DAT - Contains scheduled events information (SYSTEM)
Page 13
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
Other system files which will need to reside in the main
SPITFIRE directory include:
SFREMOTE.BAT - Used for remote Drop to DOS (SYSTEM)
SF .BAT - Invokes SPITFIRE (SYSTEM)
SFDOOR .MNU - Spitfire Door Menu (SYSTEM)
JOKER .DAT - List of undesirable caller names (SYSTEM)
DAILYLMT.DAT - Determines daily time limits, number of
downloadable files and bytes for each security
level. (SYSTEM)
SPITFIRE.HLP - Help with all commands at all menus. This file
can be modified via SFHELP.EXE. Consult the
document accompanying SFHELP.EXE. (SYSTEM)
SFPROTCO.HLP - Extra help with Uploads/Downloads. This is a
simple textfile that you can modify with your
favorite text editor, provided it saves in
ASCII format. (SYSTEM)
The SFREMOTE.BAT, SFPROTCO.HLP, SFDOOR.MNU, SF.BAT, DAILYLMT.DAT,
SPITFIRE.HLP and JOKER.DAT may be edited to your own personal tastes.
3.1 SPITFIRE WORK FILES
------------------------
The second type of file category is WORK FILES. Although not all
of these files are required to run SPITFIRE, you will find them
invaluable in the operation of your BBS system. These files are
accessed routinely and are periodically written to during the course
of SPITFIRE's execution. In the event the required work files are
not found, SPITFIRE will create them.
SFUSERS .DAT - User data file (WORK)
SFUSERS .PTR - User data pointer file (WORK)
SFMSG .DAT - All messages are contained here (WORK)
SFMSG .PTR - Message pointers for scans, etc (WORK)
CALLERS .LOG - Record of the users' activities (WORK)
HEYSYSOP.LOG - Record of special sysop notification (WORK)
SFNEWU .QUE - New user questionnaire (WORK)
SFNEWU .ANS - Contains new user questionnaire answers (WORK)
SFMAIN .QUE - Questionnaire at Main Menu for users (WORK)
SFMAIN .ANS - Answers to Main Menu Questionnaire (WORK)
SFBBSLST.DAT - Contains list of other boards to call (WORK)
Page 14
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
3.2 SPITFIRE DISPLAY FILES
--------------------------
The following files are used as display files by SPITFIRE. If
they are not found, SPITFIRE will run just the same. Most of them can
be created using your favorite text editor.
NO300 .BBS - Displayed to 300 baud users when not allowed
SFPRELOG.BBS - The first file displayed upon logon (DISPLAY)
WELCOME1.BBS/CLR - The second file displayed upon logon (DISPLAY)
WELCOME[x].BBS/CLR - Welcome2.BBS/CLR through Welcome9.BBS/CLR
are displayed in numerical order after a user
enters the name and password and gains access
to the BBS. (DISPLAY)
NEWUSER .BBS/CLR - Displayed to new user (normally rules of BBS)
(DISPLAY)
ALL .BBS CLR - The file that's displayed to all users upon
logon (DISPLAY)
BULLETIN.BBS/CLR - Lists the bulletins available to the user
(DISPLAY)
BULLET[x].BBS/CLR - [x] file is displayed when [x] bulletin is
selected. Maximum of [x] is 99 (DISPLAY)
GOODBYE .BBS/CLR - Displayed to user when logging off (DISPLAY)
TOOMANY .BBS/CLR - Displayed to user who exceeds daily limit of
calls (DISPLAY)
LOCKOUT .BBS/CLR - Displayed to a user who is marked as locked out
or is found in JOKER.DAT (DISPLAY)
NEEDSYS .BBS/CLR - Displayed to user prior to terminating connection
when utilizing the F1 key (DISPLAY)
MAXUSERS.BBS/CLR - Contains message sent to new user when maximum
amount of users is met (DISPLAY)
DLMT .BBS/CLR - Displayed to user when downloads exceed daily
limit (DISPLAY)
PRIVATE .BBS/CLR - Contains message displayed to screen if running a
private system and a new user attempts to log on
(DISPLAY)
SFPAGED .BBS/CLR - Displayed to screen if page goes unanswered
or is toggled off (DISPLAY)
SFNWSLTR .BBS/CLR - Sysop's newsletter available from the Main Menu
(DISPLAY)
SFRATIO .BBS/CLR - Displayed to user after a download if the user's
download/upload ratio exceeds your setting
(DISPLAY)
[x]SEC .BBS/CLR - Displayed to all callers of [x] security level
(DISPLAY)
[x] .BBS - Displayed to caller of user record #[x] (DISPLAY)
SFUP .BBS/CLR - Displayed to user prior to an upload (DISPLAY)
Page 15
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
SFDOWN .BBS/CLR - Displayed to user prior to a download (DISPLAY)
SFDOOR[x].BBS/CLR - Displayed to user upon entering corresponding
SPITFIRE Door program (DISPLAY)
SFDORBAK .BBS/CLR - Displayed to user upon returning to SPITFIRE
BBS after completing Door program (DISPLAY)
SFNOTIME .BBS/CLR - Displayed to user who attempts to logon after
using their daily alloted time (DISPLAY)
SFASLEEP .BBS/CLR - Displayed to user who has not entered a key-
stroke for three minutes, prior to logging
them off the BBS. (DISPLAY)
SFTIMEUP .BBS/CLR - Displayed to a user whose logon time has
expired. (DISPLAY)
SFMQDONE .BBS/CLR - Displayed to user who attempts to answer the
current main questionnaire for a second time.
(DISPLAY)
CHATDONE .BBS/CLR - Displayed to user upon completion of their chat
with the Sysop. (DISPLAY)
USERINIT .BBS/CLR - Displayed to user upon entering chat with the
Sysop if the user paged the Sysop and requested
the chat. (DISPLAY)
SYSINIT .BBS/CLR - Displayed to the user upon entering chat if the
Sysop initiated the chat. (DISPLAY)
MSGLIST .BBS/CLR - Displayed when the user responds to SPITFIRE's
prompt to list message areas available on the
BBS. (DISPLAY)
SFMSG[x] .BBS/CLR - Displayed to the user when selecting a specific
message area. [x] would correspond to the area
selected. (DISPLAY)
FILELIST .BBS/CLR - Displayed when the user responds to SPITFIRE's
prompt to list file areas available on the BBS.
(DISPLAY)
SFFILE[x].BBS/CLR - Displayed to the user when selecting a specific
file area. [x] would correspond to the area
selected. (DISPLAY)
SFBDAY .BBS/CLR - Displayed to a user on user's birthday (DISPLAY)
SFPROMSG .BBS/CLR - Displayed to the user prior to selecting a
default file transfer. Sysops should use this
display file to inform users that if a default
transfer protocol is selected, External Transfer
Procotcals will not be available to them.
(DISPLAY)
THOUGHTS .BBS - Contains thoughts created for SPITFIRE by
THOUGHTS.EXE (DISPLAY)
SFFILES .BBS - Display files which contain names of files
available for downloading in each of the file
areas on the BBS. This is the only exception to
the rule of placing a Display File in the Display
File Path. Each SFFILES.BBS should be placed in
the corresponding file area. (DISPLAY)
Page 16
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
SFEXTDN .BBS - Contains list of external download file transfer
protocols available for use. (DISPLAY)
SFEXTUP .BBS - Contains list of external upload file transfer
protocols available for use. (DISPLAY)
SPITFIRE supports the use of Ansi/Graphics display files. The
Ansi files use the file extension .CLR (color). In the event you have
Ansi/Graphics available and SPITFIRE does not find the appropriate
.CLR file to display, then the appropriate .BBS file will be displayed.
If neither file is found, SPITFIRE will, in most cases, display a
default message.
IMPORTANT: When you create display files to be used with
SPITFIRE, you must NOT have lines in these files over 255 characters
long. Further, if you make Ansi/Graphics available be sure to load the
ansi driver from within your CONFIG.SYS file.
NOTE: If you are making ANSI graphics available to your callers,
you must duplicate all display [filename].BBS files to ANSI files and
call all of them [filename].CLR. For an attractive BBS, you should
offer both sets of files.
The following list of files are an EXCEPTION to this .CLR rule:
THOUGHTS.BBS
SFFILES .BBS
SFPRELOG.BBS
NO300 .BBS
[x] .BBS
3.3 SPITFIRE MENU FILES
------------------------
Menu files contain all the information needed for SPITFIRE to
dynamically build each caller's menus, dependent on the caller's
security level.
SPITFIRE displays a function only if a caller's security level is
high enough to access it. Therefore, a caller doesn't necessarily see
every possible choice in a given menu. This places you in control and
allows you to tailor your board for your individual needs.
The format used in SFMAIN.MNU, SFSYSOP.MNU, SFMSG.MNU & SFFILE.MNU
is:
Page 17
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
Command Character, Command Description,,Security Level,Command Identifier
Knowing this, let's use the following example:
B,<B>.... Bulletins,,5,A
------------------------
The "B" is the Command Character. This will be the letter
your caller must type to access Bulletins.
"<B>.... Bulletins" is your Command Description. This is how
your file entry will be displayed in your menu on the screen.
"5" is the minimum Security Level required for the caller to
access this function...or even see it!
"A" is the SPITFIRE Command Character Identifier and should
NEVER be changed. The Command Character Identifier is
constant in SPITFIRE programming. This character will be
DIFFERENT for every command.
Once you've explored a bit, you'll find SPITFIRE allows you
to design your menus to suit your own personal taste as well as control
what commands are available to what users. The SFFILE.MNU file that
comes with the SPITFIRE package sets the <D>.... Download A File
security at 10. While a user is online, hit F2 and change a user's
security to 9 and the Download feature is gone for that user.
THERE ARE ONLY THREE RULES CONCERNING MENU LINES!:
-------------------------------------------------
You CANNOT change the Command Character Identifier from what it
now is in the unchanged menu!
You CANNOT assign the same Command Letter to two commands in the
same menu!
You CANNOT make the total length of the line more than 40
characters long.
Therefore, if you wanted, you could change Bulletins to read:
M,<M>.... Main Board,,5,A
Or, perhaps...
A,<A>.... Announcements,,5,A
Page 18
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
Just remember: NEVER change the Command Character Identifier (the
last character on each entry line), and NEVER use a Command Letter more
than once in each menu.
SPITFIRE uses the following Menu Files:
SFMAIN .MNU - Main Menu (SYSTEM)
SFMSG .MNU - Message Menu (SYSTEM)
SFFILE .MNU - File Menu (SYSTEM)
SFSYSOP .MNU - Sysop Menu (SYSTEM)
SFDOOR .MNU - Door Menu (SYSTEM)
MAIN[x] .CLR - Color Main Menu (DISPLAY)
MAIN[x] .BBS - Non-Ansi Main Menu (DISPLAY)
FILE[x] .CLR - Color File Menu (DISPLAY)
FILE[x] .BBS - Non-Ansi Main Menu (DISPLAY)
MSG[x] .CLR - Color Message Menu (DISPLAY)
MSG[x] .BBS - Non-Ansi Message Menu (DISPLAY)
SFDR[x] .CLR - Color Doors Menu (DISPLAY)
SFDR[x] .BBS - Non-Ansi Doors Menu (DISPLAY)
Refer to SPITFIRE DOORS section of this manual for information
regarding the structure of SFDOOR.MNU.
You can use EDLIN or any text editor that can create ASCII files
to edit these files.
Should you edit these menu files and come up with some real nice
looking menus, please advise so the information can be shared with
other Sysops using SPITFIRE.
SPITFIRE supports both color and Non-Ansi menus. The names of
the files displayed for the color menus are MAIN[x].CLR, FILE[x].CLR,
MSG[x].CLR and SFDR[x].CLR. The names of the Non-Ansi files displayed
for the non color menus are MAIN[x].BBS, FILE[x].BBS, MSG[x].BBS, and
SFDR[x].BBS. The "x" represents the security level of the current
caller. For example, if a caller with a security level of 10 called
and selected Ansi/Graphics, then SPITFIRE would look for files named
MAIN10.CLR, FILE10.CLR, MSG10.CLR and SFDR10.CLR to display as the
color menus. If a caller with a security level of 10 called and
choose not to use Ansi Graphics, then SPITFIRE would look for files
named MAIN10.BBS, FILE10.BBS, MSG10.BBS and SFDR10.BBS. In the event
these files are not found, then SPITFIRE will display the regular menu.
The reason for different color and Non-Ansi menu files for each
security level is to control what commands are shown to the user. For
example, if it takes a security level of 10 to be able to download a
Page 19
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
file, then FILE10.CLR and FILE10.BBS would show the <D>... Download A
File command while FILE9.CLR and FILE9.BBS would not show the command.
A color menu file and a Non-Ansi menu file will have to be created for
each security level that you assign to users if you decide to have
SPITFIRE display created menus rather than having SPITFIRE build menus.
Buffalo Creek Software provides a public domain utility to create
the color and non color menu files. The name of this utility is
MKSFMENU.EXE. You can download it from Buffalo Creek's BBS at
515-225-8496.
Sample MAIN10.CLR, FILE10.CLR, MSG10.CLR, MAIN10.BBS, FILE10.BBS
and MSG10.BBS files are furnished with your SPITFIRE package.
3.4 SPITFIRE FILE CLARIFICATIONS
---------------------------------
The following files are deserving of a more involved explanation
than what is listed previously.
DAILYLMT.DAT - If you would like to set different DAILY time
(SYSTEM) limits according to the user's security level, you
want to use this file.
The syntax is :
Security Level, Daily Time,,Daily Downloads,,,Daily Bytes,,,,Warning
EXAMPLE:
--------
10,60,,10,,,500000,,,,Y { 10 Security Level, 60 Minutes Per Day,
10 Downloads Per Day, 500,000 Bytes Per
Day, SFRATIO.BBS/CLR warning is displayed
if the U/D ratio is exceeded }
25,90,,15,,,1000000,,,,N { 25 Security Level, 90 Minutes Per Day,
15 Downloads Per Day, 1,000,000 Bytes Per
Day, SFRATIO.BBS/CLR warning is NOT
displayed if the U/D ratio is exceeded }
SFRATIO .BBS/CLR - It's rare when a caller's uploads exceed the
(DISPLAY) downloads. Some users get in the habit of taking
and never give much consideration toward
uploading. This file is displayed after a
download is completed that has tipped the scales
on the users' U/D ratio. (This U/D ratio is set
Page 20
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
at the SPITFIRE CONFIGURATION MENU, Command <15>).
SFRATIO will then be displayed, showing your
"friendly" words of advice to the user when this
situation presents itself. If you are not
concerned about a users' U/D ratio, simply don't
include this file in your SF directory.
JOKER .DAT - JOKER.DAT contains a list of all names you don't
(SYSTEM) want to allow on your board. Names like: Dr.
Phreak, Micro Muck, Lord Havoc, Nybbler, Killer,
etc.. You can create an ASCII file that has each
name listed on a separate line, such as:
Dr. Phreak
Micro Muck
Lord Havoc
Nybbler
Killer
All Users
LOCKOUT .BBS/CLR - SPITFIRE reads JOKER.DAT line-by-line and compares
(DISPLAY) the names in the file against the caller's first
and last name. If a match is found, then the
LOCKOUT.BBS/CLR is displayed to the screen and the
caller is logged off!
SFNWSLTR.BBS/CLR - File which is displayed to callers when they
(DISPLAY) request the <N>...Newsletter from the Main Menu.
This file can be used to send a special message
to the users regarding the system.
SFFILES .BBS/CLR - Used in each File Area for listing files
(DL FILE AREA) available for download in that area. This file is
set up using your favorite text editor. Here are
some guidelines one must follow for this to work
properly with SPITFIRE.
SPITFIRE.ARC 325,000 10-22-88 SPITFIRE Bulletin Board System (V2.5)
1--------10--------20--------30--------40--------50--------60--------70
The FILENAME must begin at column 1
The FILESIZE must end at column 21
The FILEDATE must end at column 31
The FILE DESCRIPTION must start at column 34
NO300 .BBS - Displays this file to 300 baud callers, when 300
(DISPLAY) baud callers are not allowed.
Page 21
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
SFREMOTE.BAT - This batch file is used with the remote Drop to
(SYSTEM) DOS feature and designed to be used with a carrier
detect utility such as WATCHDOG. If connection
is terminated while a user is at the DOS level
the system is reset provided WATCHDOG is
used. If you have included SF.BAT in the
AUTOEXEC.BAT, SPITFIRE will automatically boot on
system start up. WATCHDOG is recommended but is
not included in the SPITFIRE package because it
was written by another author (James R. Reinders,
with minor modifications by Jim Kovalsky).
However, it may be downloaded from Buffalo Creek
as well as from numerous other BBS systems.
SF .BAT - Batch file used to invoke SPITFIRE. This file
(SYSTEM) contains the necessary data for the scheduled
events feature within SPITFIRE to work properly.
(See Section 12.1 for more infomation on Scheduled
Events.) It also contains the data necessary
to execute programs using the SPITFIRE Door
feature. (See Section 16.0 for more information
on SPITFIRE Doors.)
SFPAGED .BBS/CLR - This file is displayed to the screen in the event
(DISPLAY) a user has paged the sysop and either the page
was turned off or the sysop doesn't answer.
[x]SEC .BBS/CLR - This feature is used so the sysop can send a
(DISPLAY) special notice to all users of a certain security
level. This file is not automatically erased.
(x=The security level of the users to whom you
wish to send the special message.)
[x] .BBS - This feature is used so the sysop can send a
(DISPLAY) special message to an individual user that will be
automatically erased once the user has received
it.
Example: John Doe is User Record # 95 on your system. If you have
a file named "95.BBS", SPITFIRE will display this file
when John Doe logs on and then erase it after it has been
received. Your callers log will have a notation that the
special message was sent.
Page 22
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
IMPORTANT NOTE: In the event you are using [x].BBS to send special
messages to users and you purge users from the
users file by packing the users file, please
note that the [x].BBS may no longer match the
user that you intended the message for.
3.5 ABOUT SPITFIRE DISPLAY FILES
---------------------------------
As you can see, SPITFIRE allows you complete flexibility when it
comes to displaying files. The sysop has nearly total flexibility in
making the board as unique as desired.
There are a couple of features built into the display file
routines which give you even more control. They are:
^B - Inhibits the display of the "More Prompt".
^C - Disables the callers' ability break out of the display
^D - Displays user's first name
^E - Enables the "More Prompt" if previously turned off by ^B
^P - Exhibits a "More Prompt" in the display
Place these characters in your display file. When SPITFIRE sees a
^B when displaying a file to the screen, then the <More?> prompt will
not interrupt the display. When SPITFIRE sees a ^C when displaying the
file, then the user cannot abort the screen. When SPITFIRE sees a ^D
it will display the user's first name at that point in the display.
The ^D should not be used inside a box. It causes character spaces
to be inserted when the name is entered which throws the box completely
out of line. When SPITFIRE sees a ^P the <More?> prompt is displayed
to the screen. It should be mentioned that if a ^B is present in the
same display as a ^P, it will always override the ^P prompt, nulling
the effect of the ^P feature.
^B is the extended ASCII value of 002.
^C is the extended ASCII value of 003.
^D is the extended ASCII value of 004.
^E is the extended ASCII value of 005.
^P is the extended ASCII value of 016.
3.6 BACKUP FILES
-----------------
When you perform sysop maintenance like Packing the Message Base
or Packing the Users file, SPITFIRE will first make "Backup" copies for
you. If disk space is a problem on your board you could copy the
backups to disk or discard them. They are:
Page 23
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
SFMSG .$PT - Message Pointer Backup File
SFMSG .$DA - Message Base Backup File
SFUSERS .$$$ - Users Backup File
3.7 THOUGHTS.BBS
----------------
SPITFIRE will display a THOUGHT FOR THE DAY if a file named
THOUGHTS.BBS is found in the directory in you configured as your
display file path. The program to create THOUGHTS.BBS can be
downloaded from Buffalo Creek's BBS at 515-225-8496 or you can
download a ready-made THOUGHTS.BBS file.
4.0 COMMAND LINE PARAMETERS
----------------------------
Command Line Parameters can be used to make SPITFIRE start-up with
a different configuration. Command Line Parameters are what you type
at the DOS prompt (or send to the program from a batch file) when you
boot SPITFIRE.
/Cx - Sets which COM port to use ([x] is com port).
/Ix - Initializes the System speed ([x] is modem speed).
/M - Sets the initialization string used with your
modem.
/P - Sets the drive and directory used as the SPITFIRE
Work File Path.
The use of these Command Line Parameters is not necessary, except
when you are originally booting SPITFIRE for the very first time and
then only if you are using a comm port other than comm 1 and a speed
different than 2400 baud. In other words, SPITFIRE is written to
default to comm port 1 and to initialize the system at 2400 baud so you
will not have to use Command Line Parameters unless these defaults are
different from what you plan to use while running SPITFIRE.
SPITFIRE /C2 /I9600
The above example would boot SPITFIRE utilizing COM port #2 and
initializing the system at 9600 baud rate.
It should also be mentioned that any Command Line Parameters
assigned from the DOS prompt or included in the SF.BAT file will
override those set by using ALT+Z or ALT+P at the SPITFIRE "Ready
Prompt". Anytime a change is made in the baud rate, work path,
Page 24
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
modem initialization string or comm port assignment, you MUST also
change the specifications you have set in the SF.BAT file. This is
the reason the use of command line parameters is not recommended.
4.1 SF.BAT
-----------
It is advisable to use batch files when running SPITFIRE. Here
are some advantages:
- If an error occurs, and you're using the SF.BAT enclosed
with your SPITFIRE package, SPITFIRE will automatically
reset with the SF.BAT file.
- If you have your AUTOEXEC.BAT file written to automatically
boot SPITFIRE upon system startup and you have a power
outage, then SPITFIRE will automatically reboot when power
is restored. If you should want to configure your
AUTOEXEC.BAT file to automatically boot SPITFIRE upon
system startup then the last two commands in your
AUTOEXEC.BAT file should look something like this:
CD\SF
SF
The above example assumes you are running SPITFIRE
on the drive you are booting from and you are running
SPITFIRE in a directory named SF.
5.0 SETTING UP THE SYSTEM RECORDS
-----------------------------------
There are two ways to set up the system records in SPITFIRE. The
first way is at the "Ready..." prompt you can press ALT+R. The second
way is through the Sysop Menu. Type '@' at the any menu for "Spitfire
Sysop Utilities" and then select <4>. You'll then see the following
menu:
SYSTEM RECORD NUMBER 1
Message Description : "SPITFIRE Message Area"
Message Security : 5
Message Area Access : Equal To Or Greater Than User Security
Public Message Area : All Messages Marked As Public
File Download Path : C:\SF
File Upload Path : C:\SF
File Description : "SPITFIRE File Area"
File Security : 5
File Area Access : Equal To Or Greater Than User Security
Page 25
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
SPITFIRE SYSTEM RECORD MENU
<+> Next Record <-> Previous Record
<M> Message Description <F> File Description
<U> Upload Path <D> Download Path
<B> File Security <C> Message Security
<#> Message Access <&> File Access
<R> Record Number <A> Add New Record
<P> Public/Private Message Area <Q> Quit
ENTER COMMAND - [+ - M F U D B C # & R A P Q]?
Let's start by creating/modifying the first system record. This
is done by selecting the appropriate key (considering which part of the
record you wish to modify). M, F, U, D, B, C, #, &, R, A, P, and Q
are all viable options at this point.
You will notice that the default Message Area description is
"SPITFIRE Message Area". You will want to change this to suit your
needs. You may, for example, wish to change the Description of this
area to "Public Messages". Select <M> to make this change.
The next thing you want to do is set the security level for this
Message Area. You will notice that the default security level is 5,
which means that any user with a security of 5 or greater will be able
to read messages in this area. If you wish to set a different security
level for this Message Area, then select <C> to change the security
level of the area.
You will note that SPITFIRE defaults the Message Area Access to
"Equal To Or Greater Than". What this means is that any user with a
security level equal to or greater than the security level of this
Message Area can access it. If you select <#>, SPITFIRE will toggle
this feature to "Equal To User Security". Then only users with a
security level equal to the security level of the Message Area will be
able to access this area. Users with a security level greater than or
less than the security level of this area will not be able to access
this area save those users with sysop security.
The next option available to you determines whether the Message
Area will allow private messages. The default setting of SPITFIRE
allows private messages. By selecting <P> you can toggle this feature
so that messages are marked as public.
Now you will notice that SPITFIRE sets the default download path
to the directory where SPITFIRE resides. To change this DOS filepath,
select <D> to set the path for this File Area. In the event that the
filepath set does not exist, SPITFIRE will create it. For example: If
you set your download path to C:\UTILITY and the utility directory
Page 26
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
doesn't exist on your drive, SPITFIRE will create the directory. You
will have to copy the files you want available for download into this
directory and a SFFILES.BBS (textfile) listing the files in that
directory. SFFILES.BBS must also reside in that directory. (A utility
to create your SFFILES.BBS for each file directory is available for
download from Buffalo Creek - 515-225-8496.)
To change the upload path, you simply select <U> from the menu.
The Upload and Download paths are any legal DOS pathnames telling
SPITFIRE where it can find the files associated with the File Area.
You can set uploads to go into a single "Upload file" area, or to
different areas which you could specify by subject. Here are a few
examples of upload/download paths:
The following would send the uploads to a sub-directory called
"UPLOADS" and allow the caller to download programs from a
sub-directory called "GOODIES". (Note: SF is the parent directory.):
Upload Path.......C:\SF\UPLOADS
Download Path.....C:\SF\GOODIES
The next example would send uploads to the same sub-directory
where the files available for download exist:
Upload Path.......C:\SF\GOODIES
Download Path.....C:\SF\GOODIES
If you're running on a floppy-based system with your uploads and
download files on drive B, and not using sub-directories, you could do
the following:
Upload Path.......B:\
Download Path.....B:\
You will note that SPITFIRE defaults the File Area Access to
"Equal To Or Greater Than". What this means is that any user with a
security level equal to or greater than the security level of this File
Area can access it. If you select <&>, SPITFIRE will toggle this
feature to "Equal To User Security". Then only users with a security
level equal to the security level of the File Area will be able to
access this area. Users with a security level greater than or less
than the security level of this area will not be able to access the
area save those users with sysop security.
After you've modified the present record, you are free to select
<A> from the menu to <A>dd additional areas. You can have a maximum of
40 different Message and File Areas.
Page 27
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
A system record doesn't need to contain BOTH a File AND Message
Area. You can avoid the dilemma of coupling each Message Area with a
File Area (and vice-versa) by simply setting either the File Area or
Message Area (whichever is not desired) security level higher than
any user's security level so callers can't access it or see it.
When you're done, and the record is the way you want it, simply
type <Q>. SPITFIRE will automatically save your newly configured
System Record.
6.0 SPITFIRE QUESTIONNAIRES
----------------------------
SPITFIRE uses a simple procedure to utilize Questionnaires.
Questionnaires are simple text files that are interpreted by
SPITFIRE. Any line in the file will simply be displayed to the user
unless the first character in the line is a colon ":". If the first
character in the line is a colon, then SPITFIRE displays the line and
then pauses and waits for user input.
Listed below is an example. Suppose you wish to create a poll of
what types of files your users prefer to download. Such a questionnaire
might look like this:
:What type of files interest you for download? (Games, utilities, etc.)
Thanks for your input!
If your questionnaire looks like the above example, then SPITFIRE
will show the first line to the user, pause for user input and will
display the "Thanks..." message after the user has answered the
question. The user's answer is written to either SFNEWU.ANS or
SFMAIN.ANS, depending upon which questionnaire the user is replying
to. In addition to the user's answers, the user's name, date and time
of the response is recorded within the same file.
There are 2 questionnaires available for use in SPITFIRE:
-----------------------------------------------------------------------
_
This is the NEWUSER ___/ SFNEWU .QUE The questionnaire file
Questionnaire \_SFNEWU .ANS The answer file
This is automatically displayed ONLY when a new user logs on.
Page 28
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
_
This is the POLL ___/ SFMAIN .QUE Poll questionnaire file
Questionnaire \_SFMAIN .ANS Poll answer file
This is utilized only from the MAIN MENU with <V>.. Voice Your Opinion.
Answers are appended to the end of the appropriate answer file.
If the file does not already exist, SPITFIRE will create it.
SPITFIRE requires the user to respond to the questions in the
questionnaire files before it continues.
7.0 THE FUNCTION KEYS
----------------------
F1 - Log User Off With Message
F2 - Change Security Level
F3 - Toggle Sysop Page/Prompt
F4 - Toggle Printer
F5 - Check Today's Statistics
F6 - Take Five Minutes From User
F7 - Give Five Minutes To User
F8 - Toggle Screen
F9 - Log User Off
F10 - Quit SPITFIRE
7.1 FUNCTION KEY DEFINITIONS:
------------------------------
F1 (Log User Off With Message)
-----------------------------
Displays NEEDSYS.BBS/.CLR and logs user off. If a user is ONLINE
and you need to access your system, pressing F1 displays your message
via the NEEDSYS.BBS/.CLR screen and terminates the connection.
F2 (Change Security Level)
-------------------------
If a user is ONLINE and you wish to change the user's security
level, you can change it by pressing F2. The user is unable to see
that you are changing the security level.
Page 29
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
F3 (Toggle Sysop Page)
----------------------
By toggling this parameter [ON or OFF] the sysop can decide
whether or not to be paged. If the PAGE is ON, the words "PAGE ON"
will appear on the top of your screen, provided you are using the split
screen. If the page is turned on and a user selects <P> for page, then
the prompt bell will sound to notify you that a user wishes to chat
with you. USERINIT.BBS/CLR will be displayed to the screen when you
respond to the page. If the PAGE is turned off and a user pages you,
then SFPAGED.BBS/CLR will be displayed to the user and you will not be
notified of the Page.
F4 (Toggle Printer)
-------------------
This allows you to toggle the printer ON/OFF. Everything that
is written to the CALLERS.LOG will also be sent to the printer if
this toggle is on. This is useful if you wish to retain a hard copy
of your users' activities while online. Keep in mind that your
printer must be turned on and ready for use. SPITFIRE checks to
determine if your printer is properly connected and ready for use
and responds accordingly.
F5 (Check Today's Statistics)
-----------------------------
While at the "SPITFIRE ready for caller prompt...", if you press
F5, SPITFIRE will display the name of the last caller, number of calls
for the day, number of uploads for the day and so on...
F6 (Take Five Minutes from a User)
----------------------------------
When a user is online, you can take 5 minutes from the user's
log-on time by pressing F6. If you press F6 in multiples, then
multiples of 5 minutes are taken from the user's time.
F7 (Give Five Minutes to a User)
--------------------------------
When a user is online, you can give 5 minutes to the user's log-on
time. If you press F7 in multiples, then multiples of 5 minutes are
added to the user's time.
F8 (Toggle Screen)
------------------
This feature is used to toggle the split-screen/full-screen
option. This feature can be utilized at either the "SPITFIRE ready for
caller..." prompt or when a user is online.
Page 30
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
F9 (Log User Off)
-----------------
If a user is ONLINE and you wish to disconnect this user, simply
press F9 and the connection will be terminated.
F10 (Terminate SPITFIRE)
------------------------
Pressing F10 will terminate SPITFIRE and returns you to DOS.
8.0 THE ALT KEYS
-----------------
SPITFIRE uses the ALT key in combination with a letter key for
many of its commands. Here is a list of the ALT keys used by SPITFIRE:
8.1 AVAILABLE KEYS
-------------------
ALT+A - Maintains Users File
ALT+C - Enter/Exit Chat Mode
ALT+J - Jump to DOS
ALT+M - Configure Modem
ALT+P - Configure File Paths
ALT+R - Configure System Records
ALT+S - Sysop Sign-On/Sysop Next
ALT+Q - Sysop Quick Log-On/Sysop Next
ALT+Z - Configure SPITFIRE
HOME - SPITFIRE Sysop Help Screen
The HOME key feature is available only at the "SPITFIRE ready for
caller..." prompt.
_________
/ \
__/ -+ KEY +- \__________________________________________
| |
| [O] - User must be ON-LINE to perform |
| [R] - SPITFIRE must be "Ready for caller" to perform |
| [B] - Can be used BOTH when a user's online or not. |
|_________________________________________________________|
To use an ALT+Key, the ALT key and the appropriate letter key must
be pressed simultaneously. (First, press down the ALT key, then, while
holding the ALT key down, press the letter key.)
Page 31
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
8.2 ALT KEY DEFINITIONS
------------------------
[R] ALT+A (Maintain Users File)
---------------------------------
At the "Ready..." prompt, when you select ALT+A, you can maintain
the user's file, rather than logging and maintaining the users file
from the Sysop Menu.
[O] ALT+C (Enter/Exit Chat Mode)
----------------------------------
This feature is for entering and exiting chat with a user. You
can use this feature to answer a page or force a user into chat. When
you answer a page, the caller's time online is still ticking away.
However, when you force a user into chat, the user's time online
counter is halted until the chat is finished and the user is returned
to the system.
[B] ALT+J (Jump to DOS)
-------------------------
This feature allows you to jump to DOS when you have a user online
and also when you are at the "Ready..." prompt. When you wish to go
back to SPITFIRE, type EXIT. If you are not in the proper directory
when you EXIT, SPITFIRE will automatically take you back to the
directory in which SPITFIRE resides.
[R] ALT+M (Configure Modem)
-----------------------------
This feature allows you to configure your modem initialization
string, COM port and Numeric result codes. You will also notice a
toggle switch for use of an error-checking modem. If you are using an
error-checking modem, be sure to turn this switch ON. If you are using
an error-checking modem and this switch isn't turned on, when a caller
logs on with an error-checking modem, the Ymodem-g transfer protocols
will not be available to the user.
In the event your modem requires an initialization string
different than those listed in this manual, please advise by calling
Buffalo Creek's BBS (515-225-8496), so that the information can be
passed on to other sysops.
[R] ALT+P (Configure File Paths)
---------------------------------
Pressing the ALT+P at the "SPITFIRE ready for caller..." prompt
opens a window which allows you to configure the File Paths you are
using and set whether you are using the External File Transfer
Protocols on your system. (For more information on this, refer to
Section 2.5 - File Paths.)
Page 32
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
[R] ALT+R (Configure System Records)
--------------------------------------
While SPITFIRE is at the "SPITFIRE ready for caller.." prompt, you
can select ALT+R to configure your Message and File Areas. This
feature allows you to do so without having to go through the motions of
logging on as Sysop and using the Sysop menu to make these changes.
Refer to Section 5.0 for detailed information regarding configuring
your system records.
[B] ALT+S (Log On Locally/Sysop Next)
--------------------------------------
This feature is used to log on SPITFIRE locally. It can be used
at the "Ready..." prompt or while a user is online. If you utilize
this feature while a user is online, then when the user logs off, you
are able to log-on immediately afterward. Logging on with ALT+S
will display the same initial log on display files which are displayed
to the remote users on the BBS, such as PRELOG.BBS, WELCOME1.BBS/CLR,
through WELCOME9.BBS/CLR and All.BBS/CLR.
[B] ALT+Q (Sysop Quick Log-On/Sysop Next)
-------------------------------------------
This feature is used to log on SPITFIRE locally. It can be used
at the "Ready..." prompt or while a user is online. If you utilize
this feature while a user is online, then when the user logs off, you
are able to log-on immediately afterward. Logging on with ALT+Q
will not display the initial log on display files, but rather take
you right to the Main Menu after entering your name and password.
[R] ALT+Z (Configure SPITFIRE)
--------------------------------
This feature is used to configure certain aspects of SPITFIRE.
Refer to Section 2.4, Part 5 for detailed information regarding this
portion of the SPITFIRE configuration.
"HOME" - Displays a quick summary of all keys available to the Sysop.
9.0 MAIN MENU EXPLAINED
------------------------
The Main Menu is the crux of any system, being that all major
areas of the BBS are to be accessed from this area. However, it is
important to note that a user does not have to return to the Main Menu
from the Message Section to go to the File Section (and vice-versa).
In the event there is a command on the Main Menu that you do not have
Page 33
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
functional, set the security level of that command high enough so
users cannot see it.
As the Main Menu is described and the features explained, please
keep in mind that you can control the usage of each command by changing
the security level of the commands. In other words, you can control
what commands are available to what users. (i.e. - If the security
level of the <B>.... Bulletins command is set at 25 then a user with
a security level of 24 or less would not see the command or be able to
use the command.)
The Main Menu is the first focal point your callers will see after
they have gone through the log-on screens. For the purpose of
discussion, each menu displayed will be as if the sysop (with the
highest security level) were viewing it. In this case the Main Menu
would look like this:
9.1 MAIN MENU EXAMPLE
----------------------
>>>>>>>> SPITFIRE MAIN MENU <<<<<<<<
<M>.... Message Section <F>.... Files Section
<S>.... SPITFIRE Doors <B>.... Bulletins
<C>.... Comment to Sysop <#>.... List Active Users
<L>.... Locate a User <I>.... Initial Welcome
<V>.... Voice Your Opinion <T>.... This System's Information
<N>.... Newsletter <P>.... Page the Sysop
<G>.... Goodbye & Log Off <X>.... Xpert Mode Toggle
<Y>.... Your Statistics <O>.... Other Bulletin Boards
<A>.... Add BBS Name & # <@>.... Sysop Utilities
<?>.... HELP with Commands <^D>... CTRL-D Macro
<^U>... CTRL-U Macro
MAIN MENU - [M F S B C # L I V T N P G X Y O A @ ? ^D ^U]?
9.2 EXPLANATION OF MAIN MENU FEATURES
--------------------------------------
<M>.... Message Section
This feature takes a user from the MAIN section of SPITFIRE
to the MESSAGE section.
<F>.... Files Section
This feature takes a user from the MAIN section of SPITFIRE
to the FILE section.
Page 34
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<S>.... SPITFIRE Doors
This feature allows a caller to terminate SPITFIRE so a
third party program can be run online. Normally, but not
always, the third party program is a game. When the third
party program is finished, the caller is returned to
SPITFIRE.
<B>.... Bulletins
This feature allows a user to read the available bulletins.
<C>.... Comment to Sysop
Allows a user to enter a private message to the Sysop. All
comments are automatically saved to Message Area #1.
<#>.... List Active Users
This feature will scroll the name and address of each user of
this BBS. It also shows the last date each user logged on.
<L>.... Locate a User
This feature allows a user to see if a certain person is a
user on this BBS. For example, if a user selects this
feature, then the user will be asked for a name. After a
user enters a name, SPITFIRE will check to see if that
person is a user of this BBS. SPITFIRE will advise the user
as to whether the person is a user or not. If the last name
can not be matched with a current user, SPITFIRE provides
the option of continuing to search for a user with the first
name and last name initial corresponding to what was
previously entered.
<I>.... Initial Welcome
This feature allows a user to review the opening screen.
<V>.... Voice Your Opinion
This feature allows you to poll your users on any issue you
consider of relevance to your system. This feature works in
conjunction with SFMAIN.QUE.
<T>.... This System's Info
This feature will show a user certain information about the
BBS.
<N>.... Newsletter
This feature will display SFNWSLTR.BBS (your BBS newsletter)
to the user. This can be used to keep the users updated with
changes or news concerning your BBS.
Page 35
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<P>.... Page the Sysop
This feature notifies the Sysop that a user has a question
or problem to visit about.
<G>.... Goodbye & Log Off
This feature simply allows a user to log off the BBS.
<X>.... Xpert Mode Toggle
This feature changes a user's status from a novice to an
expert or vice versa. If a user is set as a novice, then
the menu descriptions will scroll by after each command. If
a user is set as an expert, then only the command letters
scroll by after each command.
<Y>.... Your Statistics
This feature displays certain user's statistics on this BBS
and allows a user the opportunity to change some of them.
For example, this is where a user can change the keystroke
feature and where a user can write macros.
<O>.... Other Bulletin Boards
This feature will display the names and phone numbers of
other Bulletin Boards.
<A>.... Add BBS Name & #
This feature allows a user to add a name and phone number to
the BBS list described above.
<@>.... Sysop Utilities
This feature takes a user from the MAIN section to the SYSOP
section. The BBS is maintained from the SYSOP section. This
feature is not normally available to most users.
<?>.... HELP with Commands
This feature will provide help for each command available
from the MAIN MENU.
<^D>... CTRL-D Macro
Executes the ^D macro a user has written. This feature only
works if the user has written a macro.
<^U>... CTRL-U Macro
Executes the ^U macro a user has written. This feature only
works if the user has written a macro.
Page 36
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
10.0 MESSAGE MENU EXPLAINED
----------------------------
The Message Menu is the point from which your callers take part in
mail exchange. The first time they visit this area SPITFIRE will check
to see the messages they have left and notify them of the last message
they have read when they choose to read messages.
10.1 MESSAGE MENU EXAMPLE
--------------------------
>>>>>>>> SPITFIRE MESSAGE MENU <<<<<<<<
<C>.... Change Message Menu <R>.... Read Messages
<H>.... Hurry Scan Messages <B>.... Browse Messages
<N>.... Non-stop Message Capture <E>.... Enter A Message
<Y>.... Your Messages <L>.... Locate A User
<D>.... Delete a Message <T>.... Text Search
<F>.... File Section <P>.... Page the Sysop
<Q>.... Quit to MAIN MENU <S>.... SPITFIRE Doors
<X>.... Xpert Mode Toggle <G>.... Goodbye & Log Off
<@>.... Sysop Utilities <?>.... HELP with Commands
<^D>... CTRL-D Macro <^U>... CTRL-U Macro
MESSAGE MENU - [C R H B N E Y L D T F P Q S X G @ ? ^D ^U]?
10.2 MESSAGE MENU EXPLANATION
------------------------------
<C>.... Change Message Area
This feature allows a user to change to a different Message
Area. If a user selects <Q>uit, the user will remain in your
present Message Area. If a user presses the ENTER key,
SPITFIRE will list the Message Areas available to the user.
If a MSGLIST.BBS/CLR is found it will be displayed here.
<R>.... Read Messages
This feature allows a user to read public messages in a
specific Message Area or in all Message Areas. The user can
start reading the messages at a specific message or at the
last message the user read.
<H>.... Hurry Scan Messages
This feature allows a user to scan messages in a specific
Message Area or in all Message Areas. This scan doesn't
provide as much information regarding the messages as the
<B>rowse Messages feature.
Page 37
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<B>.... Browse Messages
This feature allows a user to scan messages in a specific
Message Area or in all Message Areas. This scan provides
the user with more information regarding the messages than
the <H>urry Scan Messages feature.
<N>.... Non-stop Message Capture
When this feature is executed, SPITFIRE will display all
appropriate messages non-stop. The caller normally uses
some means to capture the messages for later reading or
printing.
<E>.... Enter A Message
This feature allows a user to enter a message. If the
message the user enters is not to a specific person, then
SPITFIRE addresses the message to "All Users". If the
message is to a specific person and that person is not a
user of this BBS, then SPITFIRE will not allow the user to
enter the message. Users are allowed to send carbon copies
of a message to other users. There are a total of three
carbon copies available. There are a total of 50 lines per
message. When entering (or responding) to a message,
SPITFIRE will display the Message Areas available to you
and whether a specific Message Area allows public or
public/private messages.
<Y>.... Your Messages
This feature searches all Message Areas for messages
addressed to the user. If any messages are found, then
SPITFIRE shows the user the messages. If there are no
messages found, then SPITFIRE notifies the user that there
are no messages waiting for the user.
<L>.... Locate A User
This feature allows a user to see if a certain person is a
user on this BBS. For example, if the user selects this
feature, the user will be asked for a name. After entering a
name then SPITFIRE will check to see if that person is a user
of this BBS. If the last name can not be matched with a
current user, SPITFIRE provides the option of continuing to
search for a user with the first name and last initial that
corresponding to what was previously entered.
<D>.... Delete a Message
This feature allows a user to delete a message the user
has entered or is addressed to the user.
Page 38
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<T>.... Text Search
This feature allows a user to search for specific text in a
message. The user can decide to search for the text within
messages in a specific Message Area only or all Message
Areas. This feature will only search the user's messages
and public messages.
<F>.... File Section
This feature takes the user from the MESSAGE section of
SPITFIRE to the FILE section.
<P>.... Page the Sysop
This feature notifies the Sysop that a user has a question
or problem to visit about.
<Q>.... Quit to MAIN MENU
This feature takes a user from the MESSAGE section of
SPITFIRE to the MAIN section.
<S>.... SPITFIRE Doors
This feature allows a caller to terminate SPITFIRE so a
third party program can be run online. Normally, but not
always, the third party program is a game. When finished
with the third party program, the caller is returned
to SPITFIRE.
<X>.... Xpert Mode Toggle
This feature changes a user's status from a novice to an
expert or vice versa. If a user is set as a novice, then
the menu descriptions will scroll by after each command. If
a user is set as an expert, then only the command letters
scroll by after each command.
<G>.... Goodbye & Log Off
This feature simply allows a user to log off the BBS.
<@>.... Sysop Utilities
This feature takes a user from the MESSAGE section to the
SYSOP section. The BBS is maintained from the SYSOP section.
<?>.... HELP with Commands
This feature will provide help for each command available
from the MESSAGE MENU.
<^D>... CTRL-D Macro
Executes the ^D macro a user has written. This feature only
works if the user has written a macro.
<^U>... CTRL-U Macro
Executes the ^U macro a user has written. This feature only
works if the user has written a macro.
Page 39
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
11.0 FILE MENU EXAMPLE
-----------------------
>>>>>>>> SPITFIRE FILE MENU <<<<<<<<
<C>.... Change File Area <L>.... List Files In This Area
<E>.... Erase A File <G>.... Goodbye & Log Off
<D>.... Download a File <U>.... Upload a File
<H>.... Help on Upload/Download <P>.... Page the Sysop
<M>.... Message Section <Q>.... Quit to MAIN MENU
<S>.... SPITFIRE Doors <N>.... New Files
<T>.... Text Search Description <F>.... Find A File
<X>.... Xpert Mode Toggle <?>.... HELP with Commands
<@>.... Sysop Utilities <W>.... What's In An .ARC File
<V>.... View A Text File <^D>... CTRL-D Macro
<^U>... CTRL-U Macro
FILE MENU - [C L E G D U H P M Q S N T F X ? @ W V ^D ^U]?
11.1 FILE MENU EXPLANATION
---------------------------
<C>.... Change File Area
This feature allows a user to change to a different File
Area. If the user selects <Q>uit, the user will remain in
the same current File Area. If the user presses the ENTER
key, SPITFIRE will list the File Areas available to the user.
<L>.... List Files In This Area
This feature will display the files (SFFILES.BBS) in the
current File Area that are available for the user to
download.
<E>.... Erase A File
This feature allows a user the ability to erase a file from a
File Area. Normally this feature is only available to users
with Sysop security.
<G>.... Goodbye & Log Off
This feature simply allows a user to log off the BBS.
<D>.... Download a File
This feature simply allows a user the opportunity to download
a file, provided the user hasn't exceeded the maximum daily
download limit and provided the user has enough time left to
make the download. The user does not have to be in any
specific File Area to perform a download.
Page 40
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<U>.... Upload a File
This feature simply allows a user the opportunity to upload a
file. The user can be compensated additional time on the
BBS for the upload. The amount of the additional time is set
by the Sysop. If the user has selected an automatic file
transfer protocol, then the user can manually select a
protocol by entering a semi-colon just before the file name.
EXAMPLE...
Enter name of file: ;SPITFIRE.ARC
<H>.... Help on Upload/Download
This feature will describe the various file transfer
protocols available to the user.
<P>.... Page the Sysop
This feature notifies the Sysop that a user has a question
or problem to visit about.
<M>.... Message Section
This feature takes a user from the FILE section of SPITFIRE
to the MESSAGE section.
<Q>.... Quit to Main Menu
This feature takes a user from the FILE section of SPITFIRE
to the MAIN section.
<S>.... SPITFIRE Doors
This feature allows a caller to terminate SPITFIRE so a
third party program can be run online. Normally, but not
always, the third party program is a game. When finished
with the third party program, the caller is returned to
SPITFIRE.
<N>.... New Files
This feature allows a user to search a specific File Area or
all File Areas for files available since a specific date or
since the last time the user searched for new files.
<T>.... Text Search
This feature allows a user to search for certain text within
a file description. The user can search in a specific File
Area or in all File Areas. Please note that this feature
searches ONLY the file's description and not the file's name,
date or size. These will be displayed, however, when
matching text is located.
Page 41
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<F>.... Find A File
This feature allows a user to search a specific File Area or
all File Areas for a certain file. Wildcards are allowed.
If there is a match, the file name, size, date and
description will be shown, provided the file is listed in the
SFFILES.BBS.
<X>.... Xpert Mode Toggle
This feature changes a user's status from a novice to an
expert or vice versa. If a user is set as a novice, then
the menu descriptions will scroll by after each command. If
a user is set as an expert, then only the command letters
scroll by after each command.
<?>.... HELP with Commands
This feature will display help for each command available
from the FILE MENU. This feature is augmented with
SFHELP.EXE, which creates separate help screens for each
individual command. For more information on SFHELP.EXE,
consult the documentation accompanying it. This program is
available via download on Buffalo Creek's BBS in the
"Spitfire & Spitfire Utilities" File Area.
<@>.... Sysop Utilities
This feature takes a user from the FILE section to the SYSOP
section. The BBS is maintained from the SYSOP section. This
feature is not normally available to most users.
<W>.... What's In An .ARC File
This feature allows a user to view the contents of an .ARC
file. Presently the user will see the file name, file size
and file date of each file within the .ARC file. The user
does not have to be in a specific File Area.
<V>.... View A Text File
This feature allows a user to view a text file available for
download. The user may want to use this feature and simply
capture the text to save downloading the file. The user does
not have to be in a specific File Area to utilize this
feature.
<^D>... CTRL-D Macro
Executes the ^D macro a user has written. This feature only
works if the user has written a macro.
<^U>... CTRL-U Macro
Executes the ^U macro a user has written. This feature only
works if the user has written a macro.
Page 42
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
11.2 UPLOAD/DOWNLOAD PROTOCOLS
-------------------------------
The following is a list of Upload & Download protocols available
by SPITFIRE.
1) Ascii
2) Xmodem Checksum
3) Xmodem CRC
[* Presently D/L only] 4) 1K-Xmodem [Ymodem]
5) SEAlink Derived
* 6) Ymodem Batch
* 7) SEAlink Derived Batch
8) Ymodem-g [Error-checking modems]
* 9) Ymodem-g Batch [Error-checking modems]
It is planned to add batch uploads transfers a future release
of SPITFIRE. External Protocal file transfers are now available. (For
more information on the External Protocal feature see Section 17.0.)
There seems to be mixed feeling regarding batch uploads on a BBS.
Your input as a Sysop will be appreciated regarding this matter. It
may be that time should be spent adding other features rather than the
batch upload transfers.
12.0 SYSOP MENU EXPLAINED
--------------------------
Almost all the sysop utilities are contained in SPITFIRE. No
external programs are needed to do normal, day-to-day maintenance.
However, it is our hope that people will implement utilities for
SPITFIRE. In the event you are interested in writing such a utility
and need detailed information regarding how SPITFIRE interacts with
different support files, please feel free to contact Buffalo
Creek's BBS (515-225-8496).
>>>>>>>> SPITFIRE SYSOP MENU <<<<<<<<
<1>.... List event <2>.... Create event
<3>.... Disable event <4>.... Update system files
<5>.... Modify users <6>.... List Comments
<7>.... List Callers Log <8>.... Pack users file
<9>.... Pack Message files <A>.... Erase Alert File
<B>.... Erase Callers file <D>.... Drop to DOS
<G>.... Goodbye & Log Off <Q>.... Quit to MAIN MENU
<L>.... List Sysop Alert File <X>.... Xpert Mode Toggle
<P>.... Print Users File
Page 43
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
12.1 SYSOP MENU EXPLANATION
----------------------------
<1>.... List event
-------------------
SPITFIRE supports 13 scheduled events [A..M]. When you select
this feature, you will be asked which event [A..M] you wish to
view. If the event you select is not configured, SPITFIRE will
state that this event is not activated. If the event you select
is configured, then SPITFIRE will display the time of the event,
the day of the event, whether the event is active and whether it
has been completed that day.
<2>.... Create event
---------------------
This feature is used to create one of the 13 scheduled events
available. When you select this feature, you will be asked
which event you wish to create. If you select one that is
already active, SPITFIRE will notify you that the event selected
is already active and then ask you if you wish to change it. If
the requested event designation is not active, you will then be
asked for the time of the event (use military time. Ex: 22:00 =
10pm). Next you will be asked which day for the event. The
format looks like this:
0=Sunday, 1=Monday, 2=Tuesday, etc....7=All!
After selecting the desired scheduled event and designating the
time and day the event is to be performed, you will need to
modify the SF.BAT file with your favorite text editor. For
illustration purposes, let's assume you wish to execute Buffalo
Creek Software's SFDNLDS.EXE to create a listing of the weekly
download activity on your BBS. SFDNLDS.EXE uses the switch /F to
specify the filename that will be created with the information.
Our example will use the file BULLET1.BBS so the users may view
the file from the <B>.... Bulletin option of the Main Menu. To
simplify explanation, we will also assume all files are being run
from the SF directory, rather than individual file paths and the
event you wish to create will be event A.
First, you will need to select <2>.... Create event from the Sysop
utilities menu and then choose A as the event to be created. You
are then prompted for the time the event will be performed. Let's
assume you will enter 01:00. Next, you are prompted for the day
the event will be performed. Let's assume you wish to run the
event every Sunday so enter 0.
Page 44
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
Now, using your favorite text editor, the SF.BAT file for Event A
will look like this:
:EVENT_A
REM Place Event Commands Here
GOTO LOOP
What is required next is to include all necessary DOS commands
which are needed to run the SFDNLDS.EXE program and enter those
in place of the "REM Place Event Commands Here". A completed
SF.BAT for Event A would appear as:
:EVENT_A
SFDNLDS /F BULLET1.BBS
GOTO LOOP
With this event set up in the previously described manner, every
Sunday morning at 1:00 am, SFDNLDS would create a listing of the
BBS weekly downloads and save the information in the BULLET1.BBS
file.
IMPORTANT NOTE REGARDING SCHEDULED EVENTS!
------------------------------------------
Unique to most other Bulletin Board Systems, if a user is online
when an event is scheduled to occur, SPITFIRE waits until the user
logs off and then performs the scheduled event. In this fashion,
the user is not interrupted or subject to a forced log-off.
Please note the Event M is already configured to Pack Message
Base. At the scheduled time you designate, SPITFIRE initiates
Event M to Pack The Message Base by erasing all messages marked
for deletion and creates backup files (refer to Section 3.6).
This should be done routinely to conserve disk space.
<3>.... Disable event
----------------------
This feature is used to disable an event that you have configured.
If the event is active, SPITFIRE will ask you if you are certain
you want to disable it. In the event you answer "Yes", it will be
disabled.
<4>.... Update System Files
----------------------------
Selecting this feature performs the same functions as selecting
ALT+R at the "Ready..." prompt. Refer to Section 5.0 for more
details.
Page 45
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<5>.... Modify users
---------------------
This feature is the same as selecting ALT+A at the "Ready..."
prompt. The menu that accompanies this selection is pretty much
self-explanatory. This feature is used to change statistics on
any user.
<6>.... List Comments
----------------------
This feature searches all Message Areas for messages addressed
to you. If any messages are found, then SPITFIRE shows them to
you. If there are no messages found, then SPITFIRE notifies you
that there are no messages addressed to you.
<7>.... List Callers Log
-------------------------
When a user is online, SPITFIRE records the activities of the
user in a text file named "CALLERS.LOG". By selecting this
feature, SPITFIRE will scroll the contents of the CALLERS.LOG
file to the monitor.
<8>.... Pack Users File
------------------------
This feature allows you to pack SFUSERS.DAT. When using this
feature, SPITFIRE will purge any user marked for deletion from the
user's file. Also, SPITFIRE gives you the opportunity to purge
inactive users. When you select this feature, SPITFIRE will ask
if you wish to purge inactive users. If you answer "Y", then you
will be asked to purge users that haven't called for [x] amount
of days. The value of [x] is determined by you. Those users
who haven't logged on for [x] amount of days will then be purged
from the user's file.
<9>.... Pack Message Base
--------------------------
When you select this feature, you will be asked if you're sure you
want to pack the message base. If you answer "y", SPITFIRE goes
through the message files and purges all messages that have been
marked as deleted. SPITFIRE also provides the option of packing
messages posted prior to a specified date which you are prompted
to enter. SPITFIRE prompts you if you would like to purge old
messages. If you reply "Y" to the prompt inquiring, you are then
asked to purge messages that are [x] days old. The value of [x]
is determined by you. Any messages [x] days old will then be
purged from the message base. It is recommended that you do this
on a regular basis for a couple of reasons: [1] Disk space.
[2] Speed (SPITFIRE works faster with fewer messages).
Page 46
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<A>.... Erase Alert File
--------------------------
SPITFIRE creates and writes to a text file named "HEYSYSOP.LOG".
The contents of this file are to notify you of problems or special
features that a user may utilize, such as a file transfer
uploaded for Sysop Only. This feature gives you the opportunity
to erase "HEYSYSOP.LOG".
<B>.... Erase Callers File
----------------------------
This feature gives you the opportunity to erase the CALLERS.LOG
which was described previously. You may want to keep a permanent
record of your user's activities which are contained in this file.
In this case, you wouldn't want to delete the file, but rather
copy it to a floppy for record purposes. You will need to do
this if you are interested in conserving disk space.
<D>... Drop to DOS
-------------------
This feature allows you to drop to DOS from a remote location.
You need to use the ALT+J feature to drop to DOS locally. When
this feature is used from a remote location, SPITFIRE will not
allow the user to drop to DOS unless the drop-to-DOS password is
properly entered. This password is configured using the ALT+Z
command at the "Ready..." prompt. It is recommended that this
feature be made available to only trusted users, if made
available at all. When this feature is utilized, SPITFIRE shells
to SFREMOTE.BAT.
<G>.... Goodbye & Log Off
--------------------------
This feature simply allows you to log off the BBS.
<Q>.... Quit to MAIN MENU
--------------------------
This feature takes you from the Sysop Utility Section of SPITFIRE
to the MAIN MENU.
<L>.... List Sysop Alert File
------------------------------
SPITFIRE creates and writes to a textfile named "HEYSYSOP.LOG".
The contents of this file are to notify you of problems or special
features that a user may utilize, such as a file transfer
uploaded for Sysop Only. When this feature is selected, SPITFIRE
will display the contents of HEYSYSOP.LOG to the monitor.
Page 47
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<X>.... Xpert Mode Toggle
-------------------------
This feature changes your status from a novice to an expert or
vice versa. If you are set as a novice, then the menu
descriptions will scroll by after each command. If you are set
as an expert, then only the command letters scroll by after each
command.
<P>.... Print Users File
-------------------------
This feature prints out a hardcopy list of users' names, their
cities and phone numbers. This can only be executed locally.
13.0 SPECIAL COMMANDS FOR SYSOP STATUS
---------------------------------------
Definition of Sysop Status
--------------------------
When we refer to Sysop Status in this manual, we refer to any user
that has a security level equal to, or greater than, the Sysop security
level set using the ALT+Z feature at the "Ready..." prompt.
The Message section has a few "Special Commands" for sysop
privileged users.
It's important to note that only the sender and receiver can
delete messages, except for users with sysop security privileges, who
can read, delete, un-delete and move any message.
The <M>ove command is present so that Sysops can move a message
from one area to another.
The <P>rivate command is a toggle that can be used to make a
private message public and a public message private.
Last in the message arena is the <U>ndelete command. Anyone with
sysop privileges will automatically be able to read all the messages in
the message system, even if they have been deleted. If you see a
message which has been marked for deletion you may UN-DELETE it by
using this command. Your callers will not be able to read deleted
messages unless their access level is considered sysop level.
In the arena of file transfers, if a user with Sysop security
attempts to upload a file that already exists, then that user is given
the opportunity to overwrite the file. The user will be warned that
said file already exists and given the option to overwrite it.
SPITFIRE will not allow any other user without Sysop security this
privilege.
Page 48
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
14.0 HARDWARE/SOFTWARE DATA FLOW CONTROL
----------------------------------------
When you select ALT+M to configure your modem, you will notice
a Hardware Data Flow Control switch. This switch is turned on
(Yes) when you are using a modem that automatically adjusts to the
baud rate of the incoming call rather than depending on the software
to reset the baud rate of the comm port. If the switch is set to
Yes, then SPITFIRE will not adjust the comm port to the baud rate of
the incoming call. If the switch is set to No, then SPITFIRE will
adjust the comm port to the baud rate of the incoming call. One
case of having this switch set to YES is when you are using a USR
HST modem at 19200 baud. In this case you need to use the modem
initilization string mentioned earlier in this manual. If you are
not sure if your modem adjusts to the baud rate of the incoming call,
refer to your modem manual.
15.0 SCREEN SAVE FEATURE
-------------------------
SPITFIRE contains its own Screen Save Feature to prevent
screen-burn. If you are presently using a memory-resident screen-save
utility, it is recommended that you discontinue its usage in favor of
this feature.
16.0 SPITFIRE DOORS FEATURE
---------------------------
This feature is designed to allow the use of third party
programs (normally referred to as door programs) which are not part
of SPITFIRE but are provided by sources other than Buffalo Creek
Software. There are no door programs distributed with SPITFIRE
because these are usually Shareware products and Buffalo Creek
Software very likely has no right to distribute them with the
SPITFIRE program. However, there are many available for download
from Buffalo Creek's BBS as well as most other bulletin boards. In
the event you do not wish to run third party programs with SPITFIRE
through the Door feature, simply set the security level of the
SPITFIRE Door command in the SFMAIN.MNU, SFFILE.MNU and SFMSG.MNU files
high enough so your users cannot access it.
SPITFIRE Doors can be accessed by a caller from the Main Menu,
File Menu and Message Menu, provided the caller's security level is
high enough. SPITFIRE supports the use of 8 different doors. However,
there are third party programs that can turn these 8 doors into
hundreds of doors. One example of such a program is WILDFIRE, which
Page 49
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
is Shareware from Steve Cox. The newest release of WILDFIRE can be
downloaded from Buffalo Creek's BBS and Flite-Line BBS (402) 421-2434.
Let's configure your first door now, step by step. The first
thing to do is create a file named SFDOOR.MNU, using your favorite
text editor. Place it in your system files directory. Keep in mind
SPITFIRE only supports 8 doors so your SFDOOR.MNU file can have a
maximum of 8 lines. Since we are configuring door #1, SFDOOR.MNU will
have only 1 line. For demonstration purposes, let's write the line to
look like this:
Demo Door,10
The name of the door (as you'll have it appear in the Door Menu)
comes first in the line. You then enter a comma, which is used to
tell SPITFIRE where to end the name of the door and where to start
reading the security level of the door. In the above example, the name
of the door is "Demo Door" and it requires a security level of 10 for a
caller to be able to use it.
Now load your SF.BAT file into your favorite text editor and find
a line that reads :DOOR_1. You will place your door #1 commands (valid
DOS commands, program execution, etc.) between :DOOR_1 and GOTO LOOP.
For demonstration purposes, simply add a line that reads PAUSE between
:DOOR_1 and GOTO LOOP. That portion of your SF.BAT file should now
read as listed below:
:DOOR_1
PAUSE
GOTO LOOP
:DOOR_2
Once you have saved the changes in your SF.BAT file to disk, then
boot SPITFIRE using your SF.BAT file. At the "SPITFIRE ready for..."
prompt, log on locally either using the ALT+S or ALT+Q keystrokes.
When you get to the Main Menu, select "<S>... SPITFIRE Doors" and your
Door Menu should appear something like this:
>>>>>>>> SPITFIRE DOOR MENU <<<<<<<<
<1>... Demo Door <2>... Unavailable to you
<3>... Unavailable to you <4>... Unavailable to you
<5>... Unavailable to you <6>... Unavailable to you
<7>... Unavailable to you <8>... Unavailable to you
<Q>... Quit <G>... Goodbye
DOOR MENU - [1 2 3 4 5 6 7 8 Q G]?
Page 50
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
If you select <1> at this point, you will see a message
SPITFIRE displays that states "Executing SPITFIRE Door 1... Please
stand by!". At this point, SPITFIRE writes a read-only text file to
drive named SFDOORS.DAT and then terminates, sending the appropriate
ERROR CODE to your SF.BAT file. In the case of door #1, SPITFIRE sends
an ERROR CODE of 34 to SF.BAT which will cause the command(s) you have
placed between :DOOR_1 and GOTO LOOP to be executed. In the event you
entered a PAUSE command between :DOOR_1 and GOTO LOOP, you will then
get a "Strike a key when ready. . ." message. When you strike a key,
you will see SPITFIRE reboot and you will be prompted for your
password.
If a caller enters a door while logged on SPITFIRE, there are
three tests that must be passed for the caller to return to SPITFIRE
after exiting the door program. First, SPITFIRE must find
SFDOORS.DAT in the system files directory. Second, SPITFIRE must
find that a carrier detect exists. And third, the caller must enter
the correct password when prompted for it. In the event a door is
entered during a local log on, there are two tests that must be
passed.... SPITFIRE must find the SFDOORS.DAT file and the correct
password must be entered.
16.1 SPITFIRE DOORS DISPLAY FILES
---------------------------------
SPITFIRE will use certain display files during the use of the
Doors feature, if such files are found. It is important to note
that SPITFIRE will work just fine without these display files.
If SPITFIRE finds SFDR[x].BBS/.CLR (the [x] stands for the caller's
security level--for example, SFDR10.BBS would be displayed to a caller
with a security level of 10), this file is displayed instead of
SPITFIRE automatically building the Door Menu shown above. If
SPITFIRE finds SFDOOR[x].BBS/.CLR (the [x] stands for the number
about to be entered--for example, SFDOOR1.BBS would be shown when a
caller enters SPITFIRE Door #1), it will be displayed just before
SPITFIRE terminates for the door program execution. This file might
be used to send the caller a special message about the door. When
the caller quits the door program and returns to SPITFIRE, a file named
SFDORBAK.BBS/.CLR is displayed, if found. This file is normally used
simply to welcome the caller back to SPITFIRE.
Page 51
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
16.2 SPITFIRE DOORS SUPPORT
----------------------------
Configuring the use of doors with SPITFIRE will be supported by
Buffalo Creek Software for registered users of SPITFIRE. However,
should you have problems with the door program itself, please read the
documentation and then contact the author of the program. Please keep
in mind that once a caller has entered a door, SPITFIRE is completely
out of memory and has NO responsibility for the operation of the door
program.
17.0 EXTERNAL FILE TRANSFER PROTOCOLS
-------------------------------------
This feature is designed to allow the use of file transfer
protocols which are not part of SPITFIRE but are rather provided
by sources other than Buffalo Creek Software. An example is ZModem,
a popular protocol written by Chuck Foresburg. There are no External
Protocols distributed with SPITFIRE because they are usually
Shareware products. Buffalo Creek Software most likely has no right
to distribute them with the SPITFIRE program. However, there are
many available for download from Buffalo Creek's BBS as well as most
other bulletin boards.
It should be noted that SPITFIRE does not allow users
to select an external protocol as their default file transfer
protocol. This is important for users to know, so SPITFIRE
has provided a means to specify it:
When a new user logs on or when callers use the "<Y>... Your
Statistics" from the Main Menu to change their default file transfer
protocol, SPITFIRE will display SFPROMSG.BBS/.CLR just before a
default file transfer protocol seletion is made. The SFPROMSG.BBS/.CLR
message can state if a default file transfer protocol is chosen, the
external protocol option will not will not be available. Callers
wishing to utilize external protocols should set their default to none.
17.1 EXTERNAL DOWNLOAD PROTOCOLS
--------------------------------
SPITFIRE allows up to 9 external protocols [A..I] to be utilized
for downloads. It may be best at this point to go thru setting up
a download external protocol, step by step.
Page 52
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
To start, an assumption is being made that you have a copy of
DSZ.COM (Foresburg's ZModem). If you do not have a copy, you can
download it from Buffalo Creek's BBS. You will need to use your
favorite text editor to create a display file named SFEXTDN.BBS.
This is a simple text file which will contain the names of the
external protocols you will have available and does nothing more
than list them.
For the purpose of setting up ZModem as your first download
external protocol, your SFEXTDN.BBS file would have one line that
would look something like this:
<A> ZModem
Now place SFEXTDN.BBS in the directory you have configured as
your Display Files Path. Next, boot SPITFIRE. At the "SPITFIRE
ready for caller" prompt, simultaneously press your ALT+P keys. The
SPITFIRE FILE PATHS window will open and you need to select <4> to
set your External Transfer Path. An assumption (for demonstration
purposes) is being made here that you are running SPITFIRE on your C
drive in a directory named SF. At this point, set your External
Transfer Path to C:\SF\EXTERNAL. If a valid path has been entered,
SPITFIRE will create the directory--if one does not already exist. If
the External Transfer Protocols switch is set to "No", then toggle it
to "Yes" by selecting <1>. Now, select <Q> to Quit to the "SPITFIRE
ready for caller" prompt and then select F10 to exit SPITFIRE.
The next step is to place DSZ.COM in the directory you set as
your External Transfer Path (example... C:\SF\EXTERNAL). Next, using
your favorite text editor, create a batch file named SFEXTDNA.BAT
in the directory designated as your External Transfer Path. SPITFIRE
shells to this batch when a caller selects <A>... from the download
protocol list. It is appropriate at this point to show the suggested
contents of this batch file.
Echo Off
BRK OFF
Echo Executing SPITFIRE'S External Protocol #1
CD\SF\EXTERNAL
DSZ.COM %2 sz %3
ERASE %3
CD\SF
BRK ON
Now that SFEXTDNA.BAT, with the above listed commands, resides
in the directory you set as your External Transfer Path, you have
configured your first download External Protocol. The actual contents
Page 53
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
of the batch files you will use will depend on the specific protocols.
The above is only a sample batch file that should work fine with
DSZ.COM.
Before the commands in the above described batch file are
explained, it is important to note when a caller selects <B>...
from the download protocol list, then SPITFIRE shells to a batch file
named SFEXTDNB.BAT. As stated before, there are nine external
protocols allowed and are denoted by command letters "A" thru "I".
These command letters are used to shell SPITFIRE to the corresponding
batch files.
A = SFEXTDNA.BAT B = SFEXTDNB.BAT C = SFEXTDNC.BAT
D = SFEXTDND.BAT E = SFEXTDNE.BAT F = SFEXTDNF.BAT
G = SFEXTDNG.BAT H = SFEXTDNH.BAT I = SFEXTDNI.BAT
Now, an explanation of these batch files and what SPITFIRE does
in preparation to use these batch files is appropriate and important
for you to know and understand.
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the download. If allowable, then SPITFIRE copies the selected file
to the directory you have configured as your External Transfer Path.
PLEASE NOTE THAT SPITFIRE COPIES THE SELECTED FILE. THIS MEANS THERE
MUST BE ENOUGH DISK SPACE AVAILABLE FOR THE FILE TO BE COPIED. Now,
if all tests were passed and the file was successfully copied, then
SPITFIRE switches to the directory you have configured as your External
Transfer Path and stays in memory but shells to the appropriate batch
file (as described above). Keep in mind that SPITFIRE is resident in
memory, as well as a second copy of the command processor (COMMAND.COM)
so the external file transfer protocol is going to require some memory.
Upon performing this shell, SPITFIRE is passing at least three
parameters to the appropriate batch file. The first parameter is the
baud rate. The second parameter being passed is the number of the
comm port being used. The third parameter is the name of the file to
be downloaded. This passed information is needed by most external file
transfer programs and can now be used with DOS batch commands. The
filename is passed in ASCII text as %3. The baud rate is %1, a number
representing baud rate of the caller, such as 2400. The comm port %2
is the number of the comm port being used (1,2,3 or 4). In the event
you're are not familiar with the use of the % command in batch files,
refer to your DOS manual for specific details.
Page 54
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
When the external protocol file transfer program has finished
its work, control is automatically returned to SPITFIRE. Once control
is returned, then SPITFIRE switches back to the directory in which the
SPITFIRE system files reside. SPITFIRE then erases the file that was
copied to the directory you have configured as your External Transfer
Path for download. Last, SPITFIRE checks the amount of time that
passed during the shell to the external protocol batch file. In the
event SPITFIRE discovers that the time spent in the shell was at least
30% of the estimated transfer time, then the number of downloads,
K downloaded, etc. of the caller is updated. In the event the time
spent in the shell was less than 30% of the estimated transfer time,
then SPITFIRE assumes that the transfer was not successful and the
callers data is not updated.
You will notice the example batch file (above) has a command
to change to the directory you have configured as your External
Transfer Path. You will also notice there is a another command to
change back to the SPITFIRE system files directory. Further, you will
notice there is a command to erase the file that was copied to
the directory for download. These commands do not have to be in the
batch files you create because SPITFIRE automatically performs these
chores. However, it is quite permissible for the commands to be in
the batch file and they can act as a safeguard. You will also notice a
command BRK OFF at the beginning of the batch file example, as well as
a BRK ON at the end. BRK is a Shareware utility distributed by Solid
Systems of Newport News, Virginia. It is used to disable and enable
the CTRL BREAK, which can be used to terminate a batch file. You will
need this utility for the protection of your system. BRK.ARC can be
downloaded from Buffalo Creek's BBS.
17.2 EXTERNAL UPLOAD PROTOCOLS
------------------------------
SPITFIRE allows up to 9 external protocols [A..I] to be utilized
for uploads. Since SPITFIRE handles external protocols for uploading
slightly different than downloading, it may be best at this point to
go thru setting up an upload external protocol, step by step. To
start, an assumption is being made you have a copy of DSZ.COM
(Foresburg's ZModem). If you do not have a copy, you can download it
from Buffalo Creek's BBS. Now, you will need to use your favorite
text editor and create a display file named SFEXTUP.BBS, a simple text
file which will contain the names of the external protocols you will
have available and does nothing more than list the available protocols.
For the purpose of setting up ZModem as your first upload external
protocol, your SFEXTUP.BBS file would have one line that would look
something like this:
Page 55
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
<A> ZModem
Now place SFEXTUP.BBS in the directory you have configured as
your Display Files Path. Next, boot SPITFIRE. At the "SPITFIRE
ready for caller" prompt, simultaneously press your ALT+P keys. The
SPITFIRE FILE PATHS window will open and you need to select <4> to
set your External Transfer Path. An assumption (for demonstration
purposes) is being made here that you are running SPITFIRE on your C
drive in a directory named SF. At this point, set your External
Transfer Path to C:\SF\EXTERNAL. If a valid path has been entered,
SPITFIRE will create the directory if one does not already exist. If
the External Tranfer Protocols switch is set to "No", then toggle it
to "Yes" by selecting <1>. Now, select <Q> to Quit to the "SPITFIRE
ready for caller" prompt and then select F10 to exit SPITFIRE.
The next step is to place DSZ.COM in the directory you set as
your External Transfer Path (example... C:\SF\EXTERNAL). Next, using
your favorite text editor, create a batch file named SFEXTUPA.BAT
in the directory designated as your External Transfer Path. SPITFIRE
shells to this batch file when a caller selects <A>... from the upload
protocol list. It is appropriate at this point to show the suggested
contents of this batch file.
Echo Off
BRK OFF
Echo Executing External Protocol #1
CD\SF\EXTERNAL
DSZ.COM %2 rz
MUV %3 %4
CD\SF
BRK ON
Now that SFEXTUPA.BAT, with the above listed commands, resides
in the directory you set as your External Transfer Path, you have
configured your first upload External Protocol. The actual contents
of the batch files you will use will depend on the specific protocols.
The above is only a sample batch file and should work fine with
DSZ.COM.
Before the commands in the above described batch file are
explained, it is important to note when a caller selects <B>... from
the upload protocol list, then SPITFIRE shells to a batch file named
SFEXTUPB.BAT. As stated before, there are nine external protocols
allowed and are denoted by command letters "A" thru "I". Through
their use, SPITFIRE shells to the corresponding batch files.
Page 56
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
A = SFEXTUPA.BAT B = SFEXTUPB.BAT C = SFEXTUPC.BAT
D = SFEXTUPD.BAT E = SFEXTUPE.BAT F = SFEXTUPF.BAT
G = SFEXTUPG.BAT H = SFEXTUPH.BAT I = SFEXTUPI.BAT
Now, an explanation of these batch files and what SPITFIRE does
in preparation to use them is appropriate and important for you to
know and understand.
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the upload. If all tests were passed, then SPITFIRE changes to the
directory you have configured as your External Transfer Path and stays
resident in memory but shells to the appropriate batch file (as
described above). Keep in mind that SPITFIRE is resident in memory,
as well as a second copy of the command processor (COMMAND.COM), so the
external file transfer protocol is going to require some memory.
Upon performing this shell, SPITFIRE is passing four parameters
to the appropriate batch file. The first parameter is the baud rate.
The second parameter being passed is the number of the comm port being
used. The third parameter is the name of the file to be uploaded. The
fourth parameter is the path in which the file to be uploaded is to
reside (i.e. - C:\SF\UPLOADS). This passed information is needed by
most external file transfer programs and can now be used with DOS batch
commands. The filename is passed in ASCII text as %3. The baud rate is
%1, a number representing baud rate of the caller, such as 2400. The
comm port %2 is the number of the comm port being used (1,2,3 or 4).
In the event you're are not familiar with the use of the % command in
batch files, refer to your DOS manual for specific details.
When the external protocol file transfer program has finished
its work, control is automatically returned to SPITFIRE. Once control
is returned, then SPITFIRE changes back to the directory in which the
SPITFIRE system files reside. SPITFIRE now checks to see if the file
that was to be uploaded exists in File Area in which the uploaded file
should reside if all went correctly. If SPITFIRE finds the file in
the appropriate File Area, the caller is then credited with the upload
and other clean up chores are performed. In the event SPITFIRE does
not find the file in the appropriate File Area, then SPITFIRE assumes
the upload was aborted.
You will notice that the example batch file (above) has a command
to change to the directory you have configured as your External
Transfer Path. You will also notice there is a another command to
change back to the SPITFIRE system files directory. These commands do
not have to be in the batch files you create because SPITFIRE
automatically performs these chores. However, it is quite permissible
Page 57
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
for them to be in the batch file so they can act as a safeguard.
You will also notice a command BRK OFF at the beginning of the batch
file example, as well as a BRK ON at the end. BRK is a Shareware
utility distributed by Solid Systems of Newport News, Virginia. It
is used to disable and enable the CTRL BREAK, which can be used to
terminate a batch file. You will need this utility for the
protection of your system. BRK.ARC can be downloaded from Buffalo
Creek's BBS.
Last but not least, you will notice a command MUV %3 %4. The
file is uploaded to the directory you have configured as your
External Transfer Path and you will remember SPITFIRE must find the
file in the appropriate File Area in order for the caller to get credit
for the upload and in order for the file to be added to SFFILES.BBS.
Well, the MUV %3 %4 command will move the uploaded file to the
appropriate file area. MUV is a shareware utility by Buffalo Creek
Software that moves a file rather than copying it. MUV is available
for download from Buffalo Creek's BBS. There are a number of other
utilities that perform the same function as MUV. In the event you do
not have MUV, then you can replace the MUV %3 %4 command with the below
listed commands:
COPY %3 %4
ERASE %3
17.3 EXTERNAL PROTOCOL SUPPORT
------------------------------
Configuring the use of external file transfer protocols will be
supported by Buffalo Creek Software for registered users of SPITFIRE.
However, should you have problems with the external file transfer
program itself, please read the documentation and then contact the
author of the program.
18.0 SPITFIRE TECHNICAL REFERENCE INFORMATION
----------------------------------------------
There are absolutely no plans whatsoever to release the source
code for SPITFIRE. However, we do feel some information may be of use
to our sysops to help them understand how SPITFIRE works, and how it
handles certain routines. If there is something you would like to know
which is not covered in this documentation, please ask via Buffalo
Creek's BBS (515)-225-8496. We will make the information available to
you, if possible.
Page 58
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
There is certain information that is required for those interested
in writing utilities and other third party type programs for SPITFIRE.
Listed below are the Turbo Pascal record types that SPITFIRE uses.
TYPE
UserDefaults = (HotKey,Reserved,Pause);
MessPointer = Record
Info : Array[1..7] of String[30];
Subject : String[40];
Mdate : String[17];
Where,
NumberofRecords,
Area,OldPosition,
ReplyTo,SeeAlso : Integer;
Private,Deleted,
Received : Boolean;
End;
MessageBody = Record
MsgData : String[128];
End;
SysRecord = Record
MSec,FSec : Integer;
FDesc,MDesc,
FilePath,
UploadPath : String[60];
MEqual,
FEqual,
PublicMsgArea : Boolean;
End;
UsersPtr = Record
Name : String[30];
End;
Page 59
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
Users = Record
UserName,
CallingFrom : String[30];
Password,
TimeDate : String[14];
PhoneNumber : String[12];
BirthDate : String[8];
SecurityLevel : Integer;
Uploads,
Downloads,
TotalUK,
TotalDK : LongInt;
TimesOn,
TimeLeft,
Last_M_Area,
Last_F_Area,
TransPro : Integer;
Defaults : Set Of UserDefaults;
Macro : Array[1..2] Of String[60];
ScrollBack,
Xpert,
LockedOut,
Deleted : Boolean;
Linelen,
Pagelen,
OnToday,
Illegal,
DLToday,
ForeGround : Byte;
LastMsgRead : Integer;
DLBytes : LongInt;
NewFCheck : String[8];
Extra : String[24];
End;
Page 60
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
SysRec = Record
LastDate : String[8];
Callernum : LongInt;
CallsToday,
MsgToday,
UpToday,
DownToday,
DailyLimit,
DailyLogons,
LogonLimit,
SysopSecurityLevel,
NUS,
NUTL,
DownsPerDay,
D_URatio,
MaxUsers : Integer;
MNP1,
MNP2,
MNP3,
MNP4,
MNP5,
MNP6 : String[2];
Extran,
PrinterOn,
AnsiAvl,
Private,
SecondPassword,
Page_On,
NO300,
ErrChk : Boolean;
ModInitStr : String[56];
SysopName,
SysMsgName : String[30];
StartDate : String[18];
ComPort : Word;
MaxBaud : LongInt;
TimeComp : Real;
DOSPassword,
EXEPath : String[28];
SoftControl : Boolean;
RingNo : Integer;
DoorsAmt : Integer;
TimeToday : LongInt;
DisplayPath,
ExtranPath : String[28];
Extra : String[56];
ExtraReal : Real;
End;
Page 61
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
When a caller goes thru a Door while logged on SPITFIRE, then
SPITFIRE writes a simple read-only text file (SFDOORS.DAT) to disk.
This text file contains necessary information for the caller to
return to SPITFIRE. Below is a list of the information written to
each line of SFDOORS.DAT:
User Number (* the record number in SFUSERS.DAT of the caller *)
User Name (* the full name of the caller *)
Password (* the password of the caller *)
First Name (* the first name of the caller *)
Baud Rate (* baud rate of the caller - i.e. 2400 { 0 if local } *)
Comm port (* comm port being used by SPITFIRE *)
Time Left (* number of minutes the caller has left this log on *)
Time (* number seconds since midnight when entering the door *)
Path (* the path in which SPITFIRE.EXE resides {C:\SF\} *)
Ansi_On (* TRUE if caller is using ANSI else FALSE *)
SecLevel (* the security level of the caller *)
Uploads (* the number of uploads the caller has made *)
Downloads (* the number of downloads the caller has made *)
This Time (* total number of minutes allowed for this call *)
Time On (* number of seconds the caller has been logged on *)
Extra Time (* number of seconds the caller has gained since log on *)
19.0 COMMENT FROM THE AUTHOR
-----------------------------
This is the third release of SPITFIRE. Undoubtedly there are
features that can be added, such as additional file transfer protocols
and so forth. Your suggestions and comments will certainly be
appreciated and considered for future releases. It is believed that
this version of SPITFIRE will more than do the job for you. However,
plans are already in the making for improvements and additions. These
cover three additional file transfer protocols (including ZModem), the
ability to read a text file from within an .ARC file and more.
Hopefully, SPITFIRE will simply get better and better.
There were many people who offered suggestions and discovered
problems during the development of SPITFIRE. It would be nice to list
the names of those people but surely I would leave someone out. I do,
however, feel it important to make note that Jacque Shipley kept track
of all the changes and improvements in SPITFIRE version 2.5 and
spent a tremendous amount of time revising the manual.
Page 62
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
As mentioned earlier, SPITFIRE is written in Borland's Turbo
Pascal (v5.0). This entire program was written by Mike Woltz, however,
it would be remiss not to mention that certain code within SPITFIRE
was originally written by others. The async routines were originally
written by Edwin T. Floyd and modified by Woltz. The original SEAlink
transfer protocol code (download) was written by Jim Louvau and then
nearly totally re-written by Woltz (upload by Woltz). The original
code for viewing an .ARC file was by Woltz and then revised by Jeff
Chumbley and then re-revised by Woltz. I would be remiss if I didn't
mention that Jay Dyson, Walt Crede, Jacque Shipley and Doug Vangorp
were very instrumental in creating this manual.
It has taken over a year to get SPITFIRE to this point (maybe
I'm slow). This opportunity is taken to thank my wife Ann and my
children Mason, Jesse & Amanda for tolerating the countless number of
hours that were spent writing and testing SPITFIRE. Lord knows, I
could be a better husband and father.
20.0 SPITFIRE UTILITIES
------------------------
As utilities for SPITFIRE are written and made available, they
will be added to this manual. Inasmuch as SPITFIRE is a very new BBS
software at the time that this manual is being written, there are
still a number of utilities available. They are as listed below:
NAME AUTHOR
--------------------------------------------------------------------
THOUGHTS.ARC..................................Buffalo Creek Software
Used to maintain & create THOUGHTS.BBS.....................Shareware
SFHELP.ARC....................................Buffalo Creek Software
Used to maintain & create SPITFIRE.HLP.................Public Domain
MANAGER.ARC...................................Buffalo Creek Software
Used to maintain SPITFIRE File Areas.......................Shareware
SFLOG.ARC.....................................Buffalo Creek Software
Callers Statistical Utility............................Public Domain
MKSFMENU.ARC..................................Buffalo Creek Software
Creates menu display files for SPITFIRE................Public Domain
RECFIND.ARC...............................................Bob Hindal
Maintains SPITFIRE users file plus more....................Shareware
Page 63
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
WC2SF.ARC.............................................Jacque Shipley
Converts Wildcat BBS users file to SPITFIRE................Shareware
TOPTEN.ARC.............................................Jeff Chumbley
Creates display files for top ten users................Public Domain
B-DAY.ARC..............................................Jeff Chumbley
Creates [x].BBS files to wish users a happy birthday...Public Domain
OFFHOOK.ARC...................................Buffalo Creek Software
Used to take phone off hook for maintenance............Public Domain
PCB_SF.ARC............................................Jacque Shipley
Converts PC Board users file to SPITFIRE users file........Shareware
RBBS_SF.ARC...........................................Jacque Shipley
Converts RBBS users file to SPITFIRE users file............Shareware
FIDO_SF.ARC...........................................Jacque Shipley
Converts Fido users file to SPITFIRE users file............Shareware
WC103_SF.ARC..........................................Jacque Shipley
Converts Wildcat(v1.03) users file to SPITFIRE users file..Shareware
WC112_SF.ARC..........................................Jacque Shipley
Converts Wildcat(v1.12) users file to SPITFIRE users file..Shareware
THOTS.ARC......................................Combination of People
THOUGHTS.BBS...Over 600 "Thoughts"...Nicely done.......Public Domain
MKSFFBBS.ARC..................................Buffalo Creek Software
Used to create and maintain SFFILES.BBS................Public Domain
SFTODAY.ARC...................................Buffalo Creek Software
Used to create "Today in History" display files............Shareware
SFMKLIST.ARC..................................Buffalo Creek Software
Creates list of all or part of your files for download.....Shareware
GT_SF.ARC..............................................Dave Steinman
Converts GT Powercom users file to SPITFIRE users file.....Shareware
GEN_SF.ARC.............................................Jacque Shipley
Converts Genesis users file to SPITFIRE users file..........Shareware
SFDNLDS.ARC............................................Jacque Shipley
File listing of BBS download activity.......................Shareware
Page 64
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
WCFIL_SF.ARC...........................................Jacque Shipley
Converts Wildcat (v1.12) file listings to SPITFIRE..........Shareware
SETCHAT.ARC....................................Buffalo Creek Software
Enables setting page on/off automatically in SF.BAT.....Public Domain
Page 65
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
APPENDIX A
----------
MODEM INITIALIZATION STRINGS
----------------------------
The following is a list of modems and their corresponding initial-
ization strings which have been tested to work with SPITFIRE Bulletin
Board System.
MODEM MODEM INITIALIZATION STRING
----------------------------------------------------------------------
[1] US Robotics HST 9600......(9600 Baud)......ATS0=1Q0V0E0M0H0S2=1X1
[2] USR HST 9600..(19200 Baud)..ATS0=1&B1&N0&H3&R2&Y3Q0V0E0M0H0S2=1X1
[3] US Robotics Courier 2400...................ATS0=1Q0V0E0M0H0S2=1X1
[4] Hayes 1200..(External).....................ATS0=1Q0V0E0M0H0S2=1X1
[5] Hayes 2400..(External)..............AT&C1&D2&T5M0H0X1V0E0S2=1S0=0
[6] Everex 24...(Internal 2400).........AT&C1&D2&T5M0H0X1V0E0S2=1S0=0
Everex......(Internal 2400)...........ATM0E0V0X1&D3&T5&L1S0=0S2=1
[7] Franklin FM-2400E..........................ATS0=1Q0V0E0M0H0S2=1X1
[8] Avatex 1200 HC.............................ATS0=0Q0V0E0M0H0S2=1X1
[9] Smart One..(Best Data Products of CA)......ATS0=0Q0V0E0M0H0S2=1X1
[10] Anchor..(Internal 2400)....................ATS0=3Q0V0E0M0H0S2=1X4
[11] US Robotics Sportster...............AT&C1&D2&T5M0H0X1V0E0S2=1S0=0
[12] Commstar 2400..(Internal)..................ATS0=3Q0V0E0M0H0S2=1X4
[13] Compaq Internal 2400........................AT&F&C1&D2&B1V0S2=1&W
[14] Practical Peripheral Internal 2400..AT&C1&D2&T5M0H0X1V0E0S2=1S0=0
[15] Hayes 1200..(Internal).....................ATS0=3Q0V0E0M0H0S2=1X4
[15] Hayes 2400..(Internal).....................ATS0=3Q0V0E0M0H0S2=1X4
[16] Fastalk 2400..(External)...................ATS0=1Q0V0E0M0H0S2=1X1
[17] Magitronic MB2450..(Internal)..........AT&C1&D2M0H0X1V0E0S2=1S0=0
[18] Capetronics MD 1207...1200 Baud..............ATE0V0Q0M0S2=1S0=2X1
[19] Mikon Super Modem...(2400 External)........ATS0=0Q0M0V0E0S2=1X1&W
Page 66
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
APPENDIX B
----------
REGISTERED SPITFIRE BULLETIN BOARD SYSTEMS
------------------------------------------
As copies of SPITFIRE are registered, this manual will be revised
to list the public Bulletin Boards using registered copies SPITFIRE.
Listed below are the present public Bulletin Boards using registered
copies of SPITFIRE...
ICUL Cupboard................................515-279-1713...19200 Baud
Bear Facts BBS.....(Temporarily down)........515-285-7733...19200 Baud
Ast Turbo Byte...............................515-981-0036...19200 Baud
The Silicon Lab..............................813-869-3700...19200 Baud
The Mother Board.............................515-986-3464....9600 Baud
Sirus Cybernetics............................515-280-9107....2400 Baud
Walstreet BBS................................515-223-1113....2400 Baud
The User Surly Board.........................515-989-4486....2400 Baud
The "FOOLISH PLEASURE" BBS...................312-758-1136....2400 Baud
Roam This Fertile Land BBS...................515-288-8755....2400 Baud
ArcLink BBS..................................907-248-9625....2400 Baud
PDR BBS......................................213-821-2221....2400 Baud
Windy City BBS...............................312-735-9553....2400 Baud
Gateway AMIGA Club BBS.......................314-225-1409....2400 Baud
Park Place BBS...............................813-545-0401....2400 Baud
ASAHI BBS....................................919-444-1473....2400 Baud
Central Maryland BBS.........................301-781-7127....2400 Baud
The Henry George KnowledgeBase BBS...........818-353-2242....2400 Baud
The MainFrame BBS............................312-364-0425....2400 Baud
Hacker's BBS.................................302-322-8215....2400 Baud
Northern Illinois BBS........................815-756-8593....2400 Baud
Jim's Little Bulletin Board..................601-286-5749....2400 Baud
The Green Dragon Inn.........................515-265-7300....1200 Baud
Page 67
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
APPENDIX C
----------
SPITFIRE QUESTIONS AND ANSWERS
------------------------------
QUESTION: Why is the "Do You Want ANSI Graphics? [y/N]" displayed
each time a user logs on the BBS?
ANSWER: Some BBS software stores in the users file whether or not
a caller uses ANSI, and if so, then each time the user logs
on, ANSI graphics are automatically displayed. When creating
SPITFIRE, it was decided to provide the user with the
opportunity to select the display preferred at each log on.
There are two basic reasons for including this prompt to
each user upon log on. First, some users may call the BBS
from different locations. For instance, many users call the
BBS from work as well as from home and while they may have a
color monitor at home, they may not at work. In such a case,
they would not want to use color graphics each time they log
on. Also, observation has proven that a user may sometimes
choose Ansi graphics and other times not. This may be due to
the amount of time a user has to spend on the board since
ANSI graphics display slower than those created in ASCII.
For whatever their reasons may be, SPITFIRE demonstrates
increased flexibility by allowing the user to make that
choice.
QUESTION: With SPITFIRE at the "Ready For Caller..." prompt, the phone
rings and an incoming call is announced on the screen.
However, before the caller is connected to the BBS system,
the program returns to the "Ready For Caller..." prompt.
ANSWER: SPITFIRE relies on numeric result codes to determine the
baud rate of the incoming call. If SPITFIRE announces an
"Incoming call.." and then immediately goes back to the
"Ready for caller..." prompt, this means that your modem
sent something to SPITFIRE but not a correct result code.
This problem would indicate that the modem initialization
string is not correct. If the initialization string
contains S0=1 try changing this to S0=0 or vice versa. If
this does not remedy the situation, you should try using
another initialization string. This manual contains a list
of several initialization strings which have been tested
and are known to work with the various modems listed.
Also, please note, that the initialization string must
Page 68
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
contain the numeric character 0 (zero) and NOT the
alphabetical character O.
Once you have discovered an initialization string that works
with your modem, please report said string and the complete
name and information pertaining to your modem so this
information can be added to this manual.
QUESTION: When attempting to jump to DOS with the Alt+J command, the
screen blinks but nothing happens. What can be done to
rectify this?
ANSWER: Depending on the individual's system, occasionally the Alt+J
command which allows the Sysop to drop to DOS appears to be
inoperative. The situation can easily be corrected by
placing COMMAND.COM file in the root directory of the drive
on which SPITFIRE.EXE resides.
QUESTION: How is it possible to set up a SPITFIRE File Area without
also creating a SPITFIRE Message Area?
ANSWER: A file area can be created without having a sister message
area simply by changing the security level of the sister
message area to a security level higher than any user's
access capability. For instance, most Sysops use the
security level of 999. Setting the unused message area
security level at 1000 will prevent it from being displayed.
This same procedure can be used to prevent an unused file
area from being displayed when a sister message area is
created.
QUESTION: When a user uploads a file to "Sysop Only", how is the Sysop
made aware of the uploaded file?
ANSWER: SPITFIRE incorporates two techniques by which the Sysop is
notified that a file has been uploaded privately to them.
A message is written both in the CALLERS.LOG and also
the HEYSYSOP.LOG file that informs the Sysop that a file
has been uploaded for "Sysop Only". The CALLERS.LOG and the
HEYSYSOP.LOG file can be viewed from the Sysop Menu and
should be checked regularly to keep the Sysop aware of the
various BBS activities.
Page 69
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
QUESTION: When responding to a message, SPITFIRE requests me
to specify the Message Area I wish the reply to be
saved to. Why doesn't SPITFIRE automatically save
it to the same Message Area as the original message
I am replying to?
ANSWER: SPITFIRE allows the Sysop of each system to specify
whether each Message Area will allow only Public or
Public and Private messages. The reason SPITFIRE
does not automatically save a message reply to the
same Message Area as the original message, is to
provide the user the option of responding privately
to a message which was saved in an all Public
Message Area. For instance, if you were responding
to an all Public message and the reply was saved
to the same Message Area as the original message by
default, it would be impossible to enter a private
reply to the original message.
QUESTION: After successfully running SPITFIRE for sometime, all of
a sudden upon booting up, a message is displayed that the
SFUSERS.DAT file was not found. Why did this happen?
ANSWER: When SPITFIRE is installed a file named SFSYSDAT.SYS is
created. This file contains information as to what drive
and directory the SPITFIRE system and work files exist.
If after using the program, the Sysop changes the location
of SPITFIRE (for example, SPITFIRE was orginally booted up
on a floppy and then moved to Drive C), SPITFIRE will
continue to look for the files in the originally specified
location. The easiest way to rectify this situation is to
erase the existing SFSYSDAT.SYS file and allow a new one to
be created. SPITFIRE will automatically assign the default
path to the one in which SPITFIRE.EXE resides.
QUESTION: After adding new files to the various file areas for the
users to download, I noticed that when a caller logs
onto the BBS and does a check for new files, these files
are not displayed. What is the problem?
ANSWER: There are basically two reasons this could happen. The
first being, it is possible the files were copied into the
download directories but not added to the appropriate
SFFILES.BBS file. Another possible explanation would be
Page 70
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
that the file name, file size, file date and file
description has not been located in the exact specified
place in the SFFILES.BBS. Refer to Section 3.4 of this
manual for further information regarding this subject.
QUESTION: Why are users unable to view the contents of an .ARC file
after selecting <W>hat's In An Arc File from the File Menu.
ANSWER: This feature will only works with MS/PC DOS archive files.
If could be that the .ARC file in question was archived by
a system other than MS/PC DOS and then uploaded to your
BBS.
QUESTION: The callers log reveals "message sent and erased" for a
user who logged onto the BBS. What does this mean?
ANSWER: This would depict a special notice ( [x].BBS; refer to
Section 3.4 of the documentation for further explanation
regarding this subject) was left for a specific user. Once
the user receives this message it is automatically erased.
The CALLERS.LOG displays the above mentioned message to
inform the Sysop the message was sent and then erased.
QUESTION: The HEYSYSOP.LOG reveals a message that a specific archived
file fails the CRC check. What does this mean?
ANSWER: Anytime the Sysop is notified that an archived MS/PC DOS file
fails the CRC check, this means that the specified file is
corrupt and should be erased from your system.
Thank you very much for selecting SPITFIRE.
Page 71
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 2.5 - October 22, 1988 +-
-----------------------------------------------------------------------
NOTES: